Apps with map functionality crashing

oroboros · August 23, 2025, 6:04pm

I recently installed flightradar24 and it worked fine for a few days. Then it started crashing as soon as it launched. Afterwards I noticed that other third party apps with maps functionality are also crashing when they display a map (but oddly, not the including /e/OS Maps application.)

I’ve uninstalled every application, and cleared the cache of every native application. This hasn’t resolved the issue.

The worst effect is with EV charging apps that need to be open for payment functionality, but which default to displaying the map as soon as they are opened.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
LineageOS Version: '3.0.4-a14-20250708507309-community-lemonade'
Build fingerprint: 'OnePlus/OnePlus9/OnePlus9:13/TP1A.220905.001/R.159cc58-4e9e-182b9f:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2025-08-23 11:10:46.681615081-0600
Process uptime: 38s
Cmdline: com.coulombtech
pid: 9717, tid: 10142, name: GLThread 173  >>> com.coulombtech <<<
uid: 10234
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x000000727ec4b3f8
    x0  b4000074d473f3a0  x1  ffffffffffffffff  x2  ffffffffffffffff  x3  0000000000010301
    x4  0000000000010502  x5  b4000073946ffb58  x6  b4000073946ffb50  x7  b4000073946ffb58
    x8  0000000000000000  x9  00000000ffffffff  x10 0000000000000200  x11 0000000000000080
    x12 0000000000000081  x13 0000000000000201  x14 b4000072240b0ff0  x15 b40000727ec09ff0
    x16 0000000000000000  x17 0000000000000081  x18 00000072381b8000  x19 b400007384747000
    x20 0000000000000001  x21 0000000000000000  x22 b4000074d46ed740  x23 00000000ffffffff
    x24 00000000ffffffff  x25 000000723d978348  x26 0000000000000001  x27 0000000000000638
    x28 000000723d978240  x29 000000723d977fe0
    lr  000000723cb93a58  sp  000000723d977fe0  pc  000000723c9cf6f8  pst 00000000a0001000
17 total frames
backtrace:
  NOTE: Function names and BuildId information is missing for some frames due
  NOTE: to unreadable libraries. For unwinds of apps, only shared libraries
  NOTE: found under the lib/ directory are readable.
  NOTE: On this device, run setenforce 0 to make the libraries readable.
  NOTE: Unreadable libraries:
  NOTE:   /data/data/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
      #00 pc 000000000059c6f8  /data/data/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
      #01 pc 0000000000760a54  /data/data/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
      #02 pc 00000000005d601c  /data/data/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
      #03 pc 00000000007621c8  /data/data/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
      #04 pc 00000000004ec3bc  /data/data/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
      #05 pc 00000000004ed240  /data/data/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
      #06 pc 000000000043ce40  /data/data/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
      #07 pc 00000000003b6770  /apex/com.android.art/lib64/libart.so (art_quick_generic_jni_trampoline+144) (BuildId: 1baa085e52462906909d6dfe1b6332e2)
      #08 pc 00000000006c3394  /apex/com.android.art/lib64/libart.so (nterp_helper+7636) (BuildId: 1baa085e52462906909d6dfe1b6332e2)
      #09 pc 000000000013fc8c  /system/priv-app/GmsCore/GmsCore.apk (i7.b$c.d+676)
      #10 pc 00000000006c2514  /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 1baa085e52462906909d6dfe1b6332e2)
      #11 pc 00000000001402c4  /system/priv-app/GmsCore/GmsCore.apk (i7.b$c.run+48)
      #12 pc 000000000039ff74  /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+612) (BuildId: 1baa085e52462906909d6dfe1b6332e2)
      #13 pc 0000000000340e30  /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+144) (BuildId: 1baa085e52462906909d6dfe1b6332e2)
      #14 pc 000000000049c288  /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+1720) (BuildId: 1baa085e52462906909d6dfe1b6332e2)
      #15 pc 000000000006efbc  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 1d36f8ae6e0af6158793abea7d4f4f2b)
      #16 pc 0000000000060d60  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 1d36f8ae6e0af6158793abea7d4f4f2b)
-- Sent from /e/OS Mail.

Full recording of system during the crash: maps-crashed - Pastebin.com

Photojoe4 · August 26, 2025, 2:15am

I’m having the same issue with multiple EV charging apps. This is on a Fairphone 4. I’ve noticed at least on one that if I keep tapping the “account” tab when it’s launching I can at least get the app to load, but as soon as I go to the maps tab it crashes.

aibd · August 26, 2025, 6:29am

Here Some apps don't show info in App Lounge and can't be installed - #4 by aibd I tested Shell Recharge and the problem was MapsLibre with a linked microG issue.

4 times mentioned in OP full log but unresearched [1] is

com.google.android.gms.maps_dynamite

[1] Google MapsSDK for Android failed to load maps module - Stack Overflow

tcecyk · August 26, 2025, 10:15am

@oroboros - as to your “oddly”: /e/OS Maps uses a wholly different method for the map layer. I wonder if a reboot helps with other google maps layer apps not crashing.

that category of issue (tractive app) is when the map renders, but has missing layer styles or elements. Then the implementation is there but incomplete or embedded library not updated.

This thread ends in the mapbox / maplibre GL library segfault, possibly same crashdump (there’s no debug symbols, but stacktrace very similar) in the adb log at [kz.onay] Onay using mapbox crashes · Issue #3028 · microg/GmsCore · GitHub - I’d hook into that with the [com.coulombtech] appid to say “me too”. There was also a much older flightradar24 mapbox-gl.so library segfault, but very different stacktrace.

The segfault can go back to preceeding warnings of unimplemented methods, but can’t speak to that.

oroboros · August 26, 2025, 1:45pm

No luck with reboot, I’ve tried a few times now.

oroboros · September 4, 2025, 5:48pm

I hoped that the next system update might resolve this (if only by overwriting whatever was broken with a default). I went to 3.1.1 today but still see crashing so it looks like my next step is factory reset.

aibd · September 4, 2025, 6:35pm

I do not think that Factory reset will help.

You mention “flightradar24” [1] and “The worst effect is with EV charging apps”

I demonstrated a test on a more specific report.

Many apps can work on /e/, some cannot.

Please try another more specific report … then perhaps someone can help.

[1] Report for com.flightradar24free 10.15.1 - εxodus this gets 0/10 … for privacy, not good with a privacy focussed ROM.

tcecyk · September 6, 2025, 3:09pm

@oroboros @Photojoe4 which other EV charging apps are crashing besides those 2, can you cite more appids? (I’ll also look at com.flightradar24free if it has the same type of crash and do categorization)

Photojoe4 · September 6, 2025, 3:41pm

The two charging apps I’ve had issues crashing were Chargepoint and Blink. I can get Chargepoint to load if I continuously tap on the area where the account tab is while it’s loading, but as soon as I go to the map tab it crashes. Also, for anyone needing to use the Chargepoint app, you can also just use the website through your browser to monitor/control your charge session.

oroboros · September 6, 2025, 7:12pm

Others that crash when a map is displayed:

Some apps crash the moment that a map is displayed. Others crash after a few seconds of moving/zooming the map. The most reliable is com.evconnect.ionic which often runs for a few minutes before crashing, allowing me to view current status of chargers. com.xatori.Plugshare doesn’t reliably crash, but never displays any chargers at all (multiple spinning wheels in different places on UI suggest it has some other problem).

Loading mapbox-gl from /data/user/0/com.coulombtech/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
Loading mapbox-gl from /data/user/0/com.ea.evowner/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
Loading mapbox-gl from /data/user/0/com.evconnect.ionic/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
Loading mapbox-gl from /data/user/0/com.everbridge.mobile.iv.recipient/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
Loading mapbox-gl from /data/user/0/com.nissan.mynissan/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so
Loading mapbox-gl from /data/user/0/com.xatori.Plugshare/cache/.gmscore/lib/arm64-v8a/libmapbox-gl.so

The logs showing mapbox-gl loading are from a factory reset + fresh install of each app. I did not attempt reinstalling flightradar24 after the factory reset, and now think it was coincidental that the problem started within days of having installed it.

Photojoe4 · September 18, 2025, 3:18pm

Just an update, the Chargepoint app is now working reliably for me.

oroboros · September 21, 2025, 3:34pm

I can confirm this. Most of the other apps that were consistently crashing are now functioning as expected (except for com.nissan.mynissan, but only when I search for in-network chargers and load the map)

system · October 22, 2025, 6:04pm

This topic was automatically closed after 60 days. New replies are no longer allowed.