Technology

59594 readers

3400 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

Phone UI Always Crashes in the Same Store [Update] (lemmy.world)

submitted 1 month ago by njordomir@lemmy.world to c/technology@lemmy.world

12 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] carleeno@reddthat.com 4 points 1 month ago

I'd focus on Wi-Fi rather than BLE based on your stack trace.

You said in the previous post that even with WiFi and Bluetooth off it still happens, but did you turn off WiFi scanning as well?

Wi-Fi scanning happens even when WiFi is off, and your stack trace refers to WiFi scanning specifically.

Check your settings carefully for the WiFi scanning option. It's really only used for tracking anyway.