Phone rebooting after ending calls (upstream bug)

jmo

de0u I think since there are multiple reports that implicate a particular code path it might make sense to file an issue on the GrapheneOS issue tracker.

Done : https://github.com/GrapheneOS/os-issue-tracker/issues/4364

jmo

An answer from @muhomorr on the tracker :

This issue affects stock PIxel OS too: https://www.reddit.com/r/GooglePixel/comments/1gc78kk/android_15_pixel_6a_repeatedly_crashes_after_call/
https://support.google.com/pixelphone/thread/302961755/random-restart-after-a15?hl=en

adeyo50

jmo Another probably linked issue : if I plug the usb-c headphone during a call, it's not detected, I can't ear nor talk with it, the sound continues to come out from the phone's speaker.

I've had this issue but when I'm on a Microsoft teams call. Haven't noticed it otherwise, but it happens frequently.

jmo

According to this message, the bug is fixed but I dont get when it will the update be pushed... This is quite an annoying bug !
https://xdaforums.com/t/issue-with-pixel-6-rebooting-after-android-15-update-when-using-usb-c-buds-for-calls.4698518/#post-89799417

de0u

jmo According to this message, the bug is fixed but I dont get when it will the update be pushed...

It is quite possible that the developer inside Google doesn't know which quarterly release will include the fix. It's possible people running Google's OS might get the update via APEX... sometimes it's feasible for the GrapheneOS developers to backport...

Overall, it could easily be months.

jmo

de0u Do you know where we can find more infos on this issue ? I only found this but it's marked as won't fix !
https://issuetracker.google.com/issues/378650095

de0u

jmo Do you know where we can find more infos on this issue ?

Unfortunately I do not.

jmo I only found this but it's marked as won't fix !
https://issuetracker.google.com/issues/378650095

That one is marked as "Status: Won't Fix (Obsolete)". It's hard to be sure exactly what that means, but it could be consistent with the bug already having been fixed, hence "obsolete", even if the fix has not shipped yet.

« Previous Page