samsung-kylessopen: msm-audio card detected but increasing volume via alsamixer causes crash

There's an Audio wiki article. My guess into the wild would be, that the kernel driver is buggy and crashes when adjusting alsa controls that it does not expect; but that it would not crash if the alsa settings were adjusted that are mapped to the related Android audio stuff.

You could try to dump audio levels from Android as explained in the article if you like, or simply try to play some audio (no guarantees that this does not break your speakers or something).

By Oliver Smith on 2019-05-09T20:41:25

I'm not sure how to recover kernel panic messages on this device.

Mostly written with mainline in mind, but this might help:

https://wiki.postmarketos.org/wiki/Mainlining_FAQ#Writing_dmesg_to_RAM_and_reading_it_out_after_reboot

By Oliver Smith on 2019-05-09T20:43:17

I'll give all that a try and report back. Thanks for the suggestions.

By Ghost User on 2019-05-10T05:48:01

I tried cat /dev/urandom | aplay but it failed with: (the first line is normal, the rest are not)

Playing raw data 'stdin' : Unsigned 8 bit, Rate 8000 Hz, Mono
aplay: set_params:1403: Unable to install hw params:
ACCESS:  RW_INTERLEAVED
FORMAT:  U8
SUBFORMAT:  STD
SAMPLE_BITS: 8
FRAME_BITS: 8
CHANNELS: 1
RATE: 8000
PERIOD_TIME: 125000
PERIOD_SIZE: 1000
PERIOD_BYTES: 1000
PERIODS: 4
BUFFER_TIME: 500000
BUFFER_SIZE: 4000
BUFFER_BYTES: 4000
TICK_TIME: 0

alsamixer does display all the devices correctly, listing a front and back speaker as well as a front and back microphone. (I thought there was only one mic on the phone but I might be wrong). I'll do some more digging.

note: I've tree | grep mixer_paths.xml'd through all 14 of the kernel's I've backed up and not one of them contains that file. I've also looked inside various other related repos with no luck.

By Ghost User on 2019-05-10T15:20:52

closed

samsung-kylessopen: msm-audio card detected but increasing volume via alsamixer causes crash

Child items ...

Activity