Audio crash report

kpsmmr

Hi, My husbands been complaining for a couple of weeks that I never answer my phone.
Today I got an 'audio crash report' when he tried to ring.
As far as I know other calls come through fine but he has a different ringtone.
What do I do with the report and is there anything (fairly simple as I'm getting old and haven't kept up to date with tech really) I can do to fix it?
Also could it be related to having connected it to bluetooth on an old car stereo (which is now trying to connect all the time even when bluetooth isn't on). I'm removing that permission since I wanted it for music, not phone calls and it didn't work anyway.
TIA

type: crash
osVersion: google/lynx/lynx:14/AP2A.240905.003/2024092900:user/release-keys
uid: 1041 (u:r:hal_audio_default:s0)
cmdline: /vendor/bin/hw/android.hardware.audio.service
processUptime: 0s

signal: 11 (SIGSEGV), code 1 (SEGV_MAPERR), faultAddr 0
cause: null pointer dereference
threadName: HwBinder:838_4

de0u

kpsmmr Can you post more of the crash dump? Also, what kind of ring tone is this one: MP3, MIDI, ...? If you temporarily use that ringtone for somebody else and have that person call you, does that crash?

kpsmmr

de0u Hi, thanks for replying.
It's only happened once (the crash) and the ringtone is just one I picked from the drop down list

This is the full dump - it means absolutely nothing to me I'm afraid..

type: crash
osVersion: google/lynx/lynx:14/AP2A.240905.003/2024092900:user/release-keys
uid: 1041 (u:r:hal_audio_default:s0)
cmdline: /vendor/bin/hw/android.hardware.audio.service
processUptime: 0s

signal: 11 (SIGSEGV), code 1 (SEGV_MAPERR), faultAddr 0
cause: null pointer dereference
threadName: HwBinder:838_4

backtrace:
    /vendor/lib64/hw/audio.primary.gs201.so (event_free_common_event_client+64, pc 36b50)
    /vendor/lib64/hw/audio.platform.aoc.so (deinit_aoc_tuning_ctrl+68, pc 17764)
    /vendor/lib64/hw/audio.platform.aoc.so (aoc_card_ctrl_deinit+92, pc d69c)
    /vendor/lib64/hw/audio.primary.gs201.so (adev_close+640, pc 32f30)
    /vendor/lib64/hw/android.hardware.audio@7.1-impl.so (virtual thunk to android::hardware::audio::V7_1::implementation::Device::~Device()+92, pc 1a62c)
    /vendor/lib64/libutils.so (android::RefBase::decStrong(void const*) const+156, pc 10c9c)
    /vendor/lib64/hw/android.hardware.audio@7.1-impl.so (android::hardware::audio::V7_1::implementation::StreamOut::~StreamOut()+480, pc 2b710)
    /vendor/lib64/hw/android.hardware.audio@7.1-impl.so (virtual thunk to android::hardware::audio::V7_1::implementation::StreamOut::~StreamOut()+36, pc 2b8a4)
    /vendor/lib64/libutils.so (android::RefBase::decStrong(void const*) const+156, pc 10c9c)
    /vendor/lib64/libhidlbase.so (android::hidl::base::V1_0::BnHwBase::~BnHwBase()+188, pc 5f94c)
    /vendor/lib64/android.hardware.audio@7.1.so (android::hardware::audio::V7_1::BnHwStreamOut::~BnHwStreamOut()+192, pc 4c7e0)
    /vendor/lib64/android.hardware.audio@7.1.so (virtual thunk to android::hardware::audio::V7_1::BnHwStreamOut::~BnHwStreamOut()+36, pc 4c954)
    /vendor/lib64/libutils.so (android::RefBase::decStrong(void const*) const+156, pc 10c9c)
    /vendor/lib64/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+1444, pc 56284)
    /vendor/lib64/libhidlbase.so (android::hardware::PoolThread::threadLoop()+24, pc 55cc8)
    /vendor/lib64/libutils.so (android::Thread::_threadLoop(void*)+244, pc 115d4)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc 767ac)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 67d50)

fixed formatting for you -other8026

other8026

Looks like you have the same crash as this person: https://github.com/GrapheneOS/os-issue-tracker/issues/3832

Based on what the developer said in the issue, this crash has been reported once before, so it's not a common one. I'd try restarting to see if it happens again.

kpsmmr It's only happened once

Could be a rare bug. Hopefully it only happens just the one time for you.

kpsmmr

other8026 other8026 I found that thread too but I assumed they probably have more on their phone than I do (and I have no idea what GMS is) so I wasn't sure it was the same.

de0u

kpsmmr I found that thread too but I assumed they probably have more on their phone than I do (and I have no idea what GMS is) so I wasn't sure it was the same.

GMS = Google Mobile Services, an alternate name for the Play ecosystem.

If your husband's device does not have Play installed, and is not using any developer options, and has not been tweaked via adb or Shizuku, then adding a report to the GitHub issue might be helpful (basically, the closer the device's state is to an initial install without much stuff, the more useful the report would be). This is especially true if you have a reliable reproduction by just receiving a phone call.

The bug is almost certainly upstream, but if the GrapheneOS developers can get a sufficiently clear view into it then it may get easy enough to fix that they might have time to fix it.

kpsmmr

de0u Thank you - that's what I was wondering - if there was somewhere to send it. I will do that soon as I register with github.
It's not his phone it's mine but when he rings me it's not been ringing. I see the missed call but I don't see or hear it even if I'm next to the phone - then today it crashed. I've restarted it again and removed blue tooth permissions.
He rang me after that and I still didn't hear it from a few feet away.
Yep - there is nothing on it other than what comes with graphene except the offline map and I've had that a couple of months. I'm sure I've had all the updates - I get notifications pretty much daily. My whole point was to get rid of google!

de0u

kpsmmr There is nothing on it other than what comes with graphene except the offline map and I've had that a couple of months.

Which map?

de0u

kpsmmr It is useful to distinguish between two cases. Is it the case that you've had one crash so far, and that rebooting the device restores the device to regular operation (e.g., calls from your husband ring correctly), or is it the case that, no matter what, calls from your husband don't ring, even if the device is rebooted between calls?