Phone UI Always Crashes in the Same Store - Lemmy.World
lemmy.world
I visit a store regularly and every time to try to reference something on my phone in that store, I get UI crashes. The phone works fine everywhere else. Its a Oneplus9 running a custom rom. Two questions: 1. What could cause this? Is some sort of interference in the store crashing things? Is the bright light causing the luminosity sensor to overwhelm. Is the store trying to mess with or track my phone in some way and all my modifications, privacy configurations, etc. are choosing to crash instead of allow it? 2. Do you have any ideas about how I can figure out what is causing it? Spectrum analysis with a flipper zero or something similar, logs of some kind on the phone, process of elimination? Links are appreciated if it requires advanced nerd cred (I’m probably intermediate with Linux, Android and tech in general, except networking where my knowledge is mediocre bit growing). I am beyond curious what is going on because it is so weird that it works perfectly everywhere, but the UI keeps rebooting in this one store.

Hi folks,

About a month ago, I posted the thread at the shared link because my phone keeps spontaneously rebooting at my local Safeway store. I found several other people with similar issues online, but no one who has discovered the actual cause. I also haven’t fully understood why, but I have a few updates to share since visiting the store a few more times.

  • Scanned subGhz (w/ flipperzero) and Bluetooth frequencies. Lots of interesting things. Something bluetooth or bluetooth LE keeps popping up on the logs on my phone before the phone crashes, probably a beacon
  • Turning off Bluetooth does not stop the behavior
  • Pulled the log from the phone post-crash and it has some interesting things in it. I don’t understand it fully, but it reads like the whole system is dying due to something happening in the wifi manager?

Can anyone glean any additional information from this:

time: 1727914596869
msg: android.os.DeadSystemException: android.os.DeadSystemException
stacktrace: android.os.DeadSystemRuntimeException: android.os.DeadSystemException
	at android.net.wifi.WifiManager.getScanResults(WifiManager.java:4451)
	at com.android.systemui.statusbar.pipeline.wifi.data.repository.prod.WifiRepositoryHelper$createNetworkScanFlow$1$callback$1.onScanResultsAvailable(WifiRepositoryHelper.kt:88)
	at android.net.wifi.WifiManager$ScanResultsCallback$ScanResultsCallbackProxy$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:115)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:103)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: EmptyCoroutineContext
Caused by: android.os.DeadSystemException
	... 9 more

I think what’s happening is the phone is trying to take some kind of action based on a beacon and is crashing, but I don’t have any loyalty apps installed. Does anyone have a better understanding of how this stuff works?

  • WhyJiffie@sh.itjust.worksEnglish
    3·
    1 month ago

    it feels like that exception misses some context. I’m not familiar with kotlin, but it’s java-like and this exception cause seems unusual, like if this text would only be part of an exception chain, and if we wouldn’t see the inner (original) exception(s)

    how did you obtain this?

    • njordomir@lemmy.worldOPEnglish
      4·
      1 month ago

      When the UI crashes, it sometimes throws up a dialog with “copy URL to crash log”. I just cut and pasted from there.

      • WhyJiffie@sh.itjust.worksEnglish
        2·
        29 days ago

        you may have more success with reading the systems logs, with the ADB tool and the adb logcat command. it will probably have a lot of messages, you’ll need to filter it mentally or in a text editor