S

stkr

r134a I had '4G only' under prefered network type. I've change it to 5g or 4g (not only) and it worked. Reverted back to 4g only 2 days later.

Wow... calling with 5G allowed indeed works for me as well. Thanks a lot for the pointer. Switched to "4G only" almost a year ago to save battery. I also tried switching back to "4G only" after making a test call and now my carrier appears to refuse "4G only" uplinks entirely. Using "LTE" as preferred network now to waste power only, if necessary (i don't need any 5G features).

DeletedUser69 have you tried any of alternative dialers and if yes with what result?

Tried Fossify Phone for completeness - exactly the same behaviour in "4G only" mode (call gets cancelled immediately).

de0u Which carrier you are using might be relevant.

Congstar (German reseller of T-Mobile)

Today i noticed, that i cannot make calls (call quits immediately with a short notification sound) or be called ("caller not available at the moment").

Receiving SMS and mobile data still works, my provider already confirmed, that there are no service interruptions at the moment, it worked before at the very same location and rebooting or retrying from a new profile didn't help.

Hence i assume a "deeper" local problem on GOS, while i cannot tell, when or what it broke, because i seldomly make calls or get called on that device (build 2024121200 on a Pixel 8 Pro).

I have already exported the logs and lines containing "E", "W", "Dialer", "Telephony", "Telecom" and "AOC" appear to be relevant, but i actually have no clue, what exactly i'm looking for, which warnings or errors can be ignored and how the expected output looks like. Verbosity seems to be pretty high, so i wonder whether the content is redacted reliably to post it here.

Unfortunately resetting to factory defaults is not an option for me and i have no backup phone with the same SIM form factor to counter-check.

Any hints or ideas are appreciated. Thank you.

@Conjure6589 Did you observe the features being blocked again automatically after the call or did you have to do that manually? Sounds like a way for an unauthenticated 3rd party to control the device to some degree, if the latter.

Device tested: Pixel 8 Pro
DAC Model: Anker USB C to 3.5mm Audio Adapter
Store link: https://www.amazon.com/Anker-Adapter-Female-Samsung-Devices/dp/B08Z3B5QL3

Works out-of-the-box and comes with CTIA pin mapping compatible with all common 4-pin plugs not targeting the Chinese market.
Can't complain about audio quality, volume is a bit quiet though compared to Bluetooth headsets or the phone's built-in microphone/speaker.

@mrhappy This reply probably comes too late, but did you check, whether the loudness is just subjective and comes from dynamic compression, or the audio signal is actually clipping?
Background: I have recently tested a USB-C DAC, which is much too quiet. While i don't want too root my phone to edit mixer-paths.xml, your issues could indicate, that there might be another way to adjust microphone gain, if not solely hardware related.
Officially Android does not support gain adjustments to prevent surveillance with sensitive peripherals. However this design decision is questionable in my opinion, when leading to _15dB difference compared to the built-in microphone...