The Following User Says Thank You to Fuzzillogic For This Useful Post: | ||
![]() |
2012-02-20
, 06:31
|
Posts: 8 |
Thanked: 9 times |
Joined on Jan 2012
|
#2
|
![]() |
2012-02-20
, 12:10
|
Posts: 479 |
Thanked: 1,284 times |
Joined on Jan 2012
@ Enschede, The Netherlands
|
#3
|
![]() |
2012-02-21
, 21:39
|
Posts: 479 |
Thanked: 1,284 times |
Joined on Jan 2012
@ Enschede, The Netherlands
|
#4
|
The Following User Says Thank You to Fuzzillogic For This Useful Post: | ||
![]() |
2012-02-21
, 21:44
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#5
|
The Following User Says Thank You to woody14619 For This Useful Post: | ||
So... I forced it to 4kHz by changing the default-sample-rate in daemon.conf to 4000 and in system.pa the rate of both sinks also to 4000. Then I restarted pulseaudio (/sbin/initctl restart pulseaudio) and... a very slow system. top learned me that pulseaudio was consuming the entire CPU at high prio (dual core would be nice..) and then... crash. The device came into a boot loop.
My guess is the hardware doesn't like 4kHz, which caused the driver to $&^%-up, which caused high CPU, which caused a watchdog timer to trip, which caused the reboot.
Using the flasher --enable-rd-mode --set-rd-flags=no-lifeguard-reset the device booted again, because the watchdog is disabled (I guestimated) and I could restore both files. *pfew*
However, I'd still like to know if 44.1kHz sampling rate is indeed a good idea, but before rebricking my phone I'd like to consult the crowd here, which has much more hacking/linux experience than I
So,