[Q] [CM9] Sound stops working after waking up TP - TouchPad Q&A, Help & Troubleshooting
I made this post in the CM9 thread but I thought Id make a thread here to see if anyone is experiencing the same problem as me.
I've been having a recurring problem with my TP since a while back. My sound stops working when i wake my device up after deepsleep. the only way to get sound working again is to reboot. Installing the bricked-ics kernel fixed this but that kernel was unstable. Ive tried removing android completely from my device, done a webosdoctor and then reinstalling it. Still the same problem. Ive had this since after the 3.5 alpha. im on the latest nightly now.
I've taken some catlogs of when the sound is working after a fresh reboot and one where its not. These catlogs are me pressing on the menu button to try to make a touchsound.
Without sound
Code:
04-20 03:21:39.499 D/dalvikvm(9013): GC_FOR_ALLOC freed 1K, 17% free 11218K/13447K, paused 26ms
04-20 03:21:40.419 D/dalvikvm(9013): GC_FOR_ALLOC freed 276K, 18% free 11073K/13447K, paused 27ms
04-20 03:21:41.219 I/ALSAModule(196): ALSA Module: closing down output device
04-20 03:21:42.429 I/ALSAModule(196): ALSA Module: closing down output device
04-20 03:21:42.449 D/memalloc(193): /dev/pmem: Allocated buffer base:0x2ca68000 size:1638400 offset:3014656 fd:37
04-20 03:21:42.459 D/memalloc(2045): /dev/pmem: Mapped buffer base:0x48a63000 size:4653056 offset:3014656 fd:85
04-20 03:21:42.459 D/ALSAModule(196): open called for devices 00000000 in mode 0...
04-20 03:21:42.489 I/ALSAModule(196): Set global parms
04-20 03:21:42.489 I/ALSAModule(196): Setting interleved PCM
04-20 03:21:42.519 D/memalloc(193): /dev/pmem: Allocated buffer base:0x2ca68000 size:1638400 offset:4653056 fd:41
04-20 03:21:42.549 I/ALSAModule(196): Buffer size: 2400, chunk 4800, latency 54421
04-20 03:21:42.549 I/ALSAModule(196): Initialized ALSA PLAYBACK device default
04-20 03:21:42.549 E/AudioHardwareALSA(196): RE-OPEN AFTER STANDBY:: took 121 msecs
04-20 03:21:42.549 D/memalloc(2045): /dev/pmem: Mapped buffer base:0x48ed3000 size:6291456 offset:4653056 fd:88
04-20 03:21:42.569 D/memalloc(193): /dev/pmem: Allocated buffer base:0x2ca68000 size:1638400 offset:6291456 fd:52
04-20 03:21:42.579 D/memalloc(2045): /dev/pmem: Mapped buffer base:0x4ab66000 size:7929856 offset:6291456 fd:91
With sound
Code:
04-20 03:44:29.099 D/NetlinkEvent(149): Unexpected netlink message. type=0x0
04-20 03:44:29.709 D/NetlinkEvent(149): Unexpected netlink message. type=0x140e
04-20 03:44:33.549 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:393216 offset:0 fd:36
04-20 03:44:33.549 D/memalloc(1588): /dev/pmem: Mapped buffer base:0x47d3e000 size:393216 offset:0 fd:46
04-20 03:44:33.589 I/ALSAModule(156): ALSA Module: closing down output device
04-20 03:44:33.629 D/ALSAModule(156): open called for devices 00000000 in mode 0...
04-20 03:44:33.659 I/ALSAModule(156): Set global parms
04-20 03:44:33.659 I/ALSAModule(156): Setting interleved PCM
04-20 03:44:33.679 I/ALSAModule(156): Buffer size: 2400, chunk 4800, latency 54421
04-20 03:44:33.679 I/ALSAModule(156): Initialized ALSA PLAYBACK device default
04-20 03:44:33.679 E/AudioHardwareALSA(156): RE-OPEN AFTER STANDBY:: took 87 msecs
04-20 03:44:33.749 D/dalvikvm(1588): GC_CONCURRENT freed 385K, 33% free 7695K/11335K, paused 2ms+15ms
04-20 03:44:35.399 D/memalloc(1588): /dev/pmem: Unmapping buffer base:0x47d3e000 size:393216 offset:0
04-20 03:44:35.419 W/InputManagerService(229): Window already focused, ignoring focus gain of: [email protected]
04-20 03:44:35.659 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2ca66000 size:393216 offset:0 fd:36
04-20 03:44:38.769 I/ALSAModule(156): ALSA Module: closing down output device
04-20 03:44:38.869 I/ALSAModule(156): ALSA Module: closing down output device
04-20 03:44:38.899 D/ALSAModule(156): open called for devices 00000000 in mode 0...
04-20 03:44:38.929 I/ALSAModule(156): Set global parms
04-20 03:44:38.929 I/ALSAModule(156): Setting interleved PCM
04-20 03:44:38.989 I/ALSAModule(156): Buffer size: 2400, chunk 4800, latency 54421
04-20 03:44:38.989 I/ALSAModule(156): Initialized ALSA PLAYBACK device default
04-20 03:44:38.989 E/AudioHardwareALSA(156): RE-OPEN AFTER STANDBY:: took 118 msecs
04-20 03:44:39.209 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:393216 offset:0 fd:36
04-20 03:44:39.219 D/memalloc(1588): /dev/pmem: Mapped buffer base:0x47d3e000 size:393216 offset:0 fd:46
04-20 03:44:41.159 D/memalloc(1588): /dev/pmem: Unmapping buffer base:0x47d3e000 size:393216 offset:0
04-20 03:44:41.169 W/InputManagerService(229): Window already focused, ignoring focus gain of
I am experiencing the exact same issue and have been since applying first nightly build + 1 month ago.
Also followed the same process as OP, tried bricked kernel which did solve audio issue but was too unstable. Removed Android, wiped device, doctored new WebOS and reinstalled latest nightly build, issue still persists.
After reboot, sound works fine. Anytime screen turns off or device goes into sleep, or if I turn the screen off, when it comes back on no sound at all until next reboot. Have tried raising min CPU state, voltages, etc... with no resolution.
greatgreek said:
I am experiencing the exact same issue and have been since applying first nightly build + 1 month ago.
Also followed the same process as OP, tried bricked kernel which did solve audio issue but was too unstable. Removed Android, wiped device, doctored new WebOS and reinstalled latest nightly build, issue still persists.
After reboot, sound works fine. Anytime screen turns off or device goes into sleep, or if I turn the screen off, when it comes back on no sound at all until next reboot. Have tried raising min CPU state, voltages, etc... with no resolution.
Click to expand...
Click to collapse
It seems to be an issue not many people know or care about.
I recorded another logcat, that could help. Wish someone would take a look at it.
Code:
build.board: tenderloin
build.bootloader: unknown
build.brand: generic
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: tenderloin
build.display: IMM76D
build.fingerprint: hp/hp_tenderloin/tenderloin:4.0.4/IMM76D/223971:user/release-keys
build.hardware: tenderloin
build.host: marjory
build.id: IMM76D
build.manufacturer: unknown
build.model: cm_tenderloin
build.product: touchpad
build.radio: unknown
build.serial: 6d2092c8a14f55aa15b6b794e3cdd6a6e1fd97e1
build.tags: test-keys
build.time: 1334763995000
build.type: userdebug
build.user: cm-hudson
version.codename: REL
version.incremental: eng.cm-hudson.20120418.094527
version.release: 4.0.4
version.sdk_int: 15
04-20 19:00:49.289 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:00:49.309 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:73728 offset:18612224 fd:39
04-20 19:00:49.319 D/memalloc(1490): /dev/pmem: Mapped buffer base:0x46e90000 size:18685952 offset:18612224 fd:70
04-20 19:00:49.319 D/ALSAModule(155): open called for devices 00000000 in mode 0...
04-20 19:00:49.349 I/ALSAModule(155): Set global parms
04-20 19:00:49.349 I/ALSAModule(155): Setting interleved PCM
04-20 19:00:49.549 I/ALSAModule(155): Buffer size: 2400, chunk 4800, latency 54421
04-20 19:00:49.549 I/ALSAModule(155): Initialized ALSA PLAYBACK device default
04-20 19:00:49.549 E/AudioHardwareALSA(155): RE-OPEN AFTER STANDBY:: took 262 msecs
04-20 19:00:49.729 D/dalvikvm(1490): GC_CONCURRENT freed 992K, 17% free 6919K/8263K, paused 3ms+5ms
04-20 19:00:51.919 D/dalvikvm(517): GC_FOR_ALLOC freed 278K, 10% free 7375K/8135K, paused 24ms
04-20 19:00:52.739 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:00:52.799 D/memalloc(1490): /dev/pmem: Unmapping buffer base:0x46e90000 size:18685952 offset:18612224
04-20 19:00:53.339 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2dc26000 size:73728 offset:18612224 fd:39
04-20 19:00:56.809 I/lights (221): Disabling touch screen
04-20 19:00:56.809 D/lights (221): Send ts socket 1 byte(s): 'C'
04-20 19:00:56.809 D/ts_srv (148): Socket received 1 byte(s): 'C'
04-20 19:00:56.809 D/ts_srv (148): uart closed: 0
04-20 19:00:56.809 I/ts_power(148): touchscreen_power: enable=0, ts_state=1
04-20 19:00:56.809 I/power (221): *** set_screen_state 0
04-20 19:00:56.809 D/SurfaceFlinger(152): About to give-up screen, flinger = 0xf918
04-20 19:00:56.809 D/Sensors (221): sensor activation called: handle=3, enabled=0********************************
04-20 19:00:56.819 D/Sensors (221): sensor activation called: handle=0, enabled=0********************************
04-20 19:00:56.829 V/TransportControlView(221): Create TCV [email protected]
04-20 19:00:56.889 D/dalvikvm(221): GC_FOR_ALLOC freed 610K, 13% free 10026K/11463K, paused 44ms
04-20 19:00:56.919 I/CpuGovernorService(221): intent action: android.intent.action.SCREEN_OFF
04-20 19:00:56.979 D/dalvikvm(221): GC_FOR_ALLOC freed 66K, 9% free 10432K/11463K, paused 37ms
04-20 19:00:57.049 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:00:57.089 D/ALSAModule(155): open called for devices 00000000 in mode 0...
04-20 19:00:57.109 D/dalvikvm(221): GC_EXPLICIT freed 21K, 9% free 10493K/11527K, paused 2ms+11ms
04-20 19:00:57.119 I/ALSAModule(155): Set global parms
04-20 19:00:57.119 I/ALSAModule(155): Setting interleved PCM
04-20 19:00:57.119 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:3014656 offset:12582912 fd:39
04-20 19:00:57.139 D/memalloc(221): /dev/pmem: Mapped buffer base:0x4c6b3000 size:15597568 offset:12582912 fd:255
04-20 19:00:57.149 I/TabletStatusBar(354): DISABLE_CLOCK: yes
04-20 19:00:57.179 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:3014656 offset:19005440 fd:43
04-20 19:00:57.189 D/memalloc(221): /dev/pmem: Mapped buffer base:0x4e51e000 size:22020096 offset:19005440 fd:258
04-20 19:00:57.309 I/ALSAModule(155): Buffer size: 2400, chunk 4800, latency 54421
04-20 19:00:57.309 I/ALSAModule(155): Initialized ALSA PLAYBACK device default
04-20 19:00:57.309 E/AudioHardwareALSA(155): RE-OPEN AFTER STANDBY:: took 257 msecs
04-20 19:00:57.359 D/dalvikvm(1490): GC_CONCURRENT freed 239K, 15% free 7081K/8263K, paused 4ms+6ms
04-20 19:00:57.539 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:3014656 offset:6029312 fd:54
04-20 19:00:57.549 D/memalloc(221): /dev/pmem: Mapped buffer base:0x4d593000 size:9043968 offset:6029312 fd:264
04-20 19:01:00.229 W/ThrottleService(221): unable to find stats for iface rmnet0
04-20 19:01:00.549 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:01:31.889 D/dalvikvm(517): GC_FOR_ALLOC freed 258K, 10% free 7374K/8135K, paused 27ms
04-20 19:03:47.730 I/power (221): *** set_screen_state 1
04-20 19:03:47.760 D/Sensors (221): sensor activation called: handle=3, enabled=1********************************
04-20 19:03:47.770 D/Sensors (221): sensor activation called: handle=0, enabled=1********************************
04-20 19:03:47.800 I/CpuGovernorService(221): intent action: android.intent.action.SCREEN_ON
04-20 19:03:47.800 E/WifiStateMachine(221): set suspend optimizations failed!
04-20 19:03:47.830 I/lights (221): Enabling touch screen
04-20 19:03:47.830 D/lights (221): Send ts socket 1 byte(s): 'O'
04-20 19:03:47.830 D/ts_srv (148): Socket received 1 byte(s): 'O'
04-20 19:03:47.830 I/ts_power(148): touchscreen_power: enable=1, ts_state=0
04-20 19:03:47.830 I/WindowManager(221): Lock screen displayed!
04-20 19:03:48.010 D/SurfaceFlinger(152): Screen about to return, flinger = 0xf918
04-20 19:03:48.030 D/ts_srv (148): uart opened at 15
04-20 19:03:48.150 D/dalvikvm(1490): GC_CONCURRENT freed 365K, 15% free 7105K/8263K, paused 2ms+3ms
04-20 19:03:48.920 D/dalvikvm(517): GC_FOR_ALLOC freed 258K, 10% free 7374K/8135K, paused 34ms
04-20 19:03:49.340 D/OpenGLRenderer(221): Flushing caches (mode 0)
04-20 19:03:49.350 D/memalloc(221): /dev/pmem: Unmapping buffer base:0x4c6b3000 size:15597568 offset:12582912
04-20 19:03:49.350 D/memalloc(221): /dev/pmem: Unmapping buffer base:0x4e51e000 size:22020096 offset:19005440
04-20 19:03:49.350 D/memalloc(221): /dev/pmem: Unmapping buffer base:0x4d593000 size:9043968 offset:6029312
04-20 19:03:49.350 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2d666000 size:3014656 offset:12582912 fd:39
04-20 19:03:49.350 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2d026000 size:3014656 offset:6029312 fd:54
04-20 19:03:49.360 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:03:49.380 D/dalvikvm(354): GC_CONCURRENT freed 430K, 8% free 7657K/8263K, paused 4ms+1ms
04-20 19:03:49.380 D/ALSAModule(155): open called for devices 00000000 in mode 0...
04-20 19:03:49.400 I/TabletStatusBar(354): DISABLE_CLOCK: no
04-20 19:03:49.410 I/ALSAModule(155): Set global parms
04-20 19:03:49.410 I/ALSAModule(155): Setting interleved PCM
04-20 19:03:49.440 V/TabletStatusBar(354): setLightsOn(true)
04-20 19:03:49.470 I/ALSAModule(155): Buffer size: 2400, chunk 4800, latency 54421
04-20 19:03:49.470 I/ALSAModule(155): Initialized ALSA PLAYBACK device default
04-20 19:03:49.470 E/AudioHardwareALSA(155): RE-OPEN AFTER STANDBY:: took 113 msecs
04-20 19:03:49.500 W/InputManagerService(221): Window already focused, ignoring focus gain of: [email protected]
04-20 19:03:49.610 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2dc86000 size:3014656 offset:19005440 fd:43
04-20 19:03:52.670 I/ALSAModule(155): ALSA Module: closing down output device
Since bricked kernel fixed the problem, and kupdate kernel didn't help, give this kernel a try :
http://forum.xda-developers.com/showthread.php?t=1578819
Hope it helps.
I found out today that if you keep headphones in your TP, the sound wont stop working even if your TP goes into deep sleep. So that's something to help figure this out i guess.
I'm using my SGSII headphones, with the extra microphone ring btw, so that might be the problem? Anyone using headphones with built in microphones.
There's a free app in market (play, now, I guess) called Audio Manager. It has a lot of settings. I don't know if this will help, but it's worth a try.
That's good to know about the earphones/headphones. I knew that if you plugged them in before starting the media player, they would work (for those whose earphones/headphones weren't working).
After Headphones plugged in
I didn't have this issue until after I plugged in my headphones. This error also is affecting the vibration of the touchpad. I read that if you power off the device then plug in headphones, boot the device with headphones attached, then unplug the headphones once booted the error should be fixed.
Possible fix
Read in another thread that rebooting device with headphones plugged in would resolve this issue - was skeptical but tried it.
It worked for me.
Powered down my TP. Inserted headphones. Powered up and booted into CM9. After boot complete, played sound which came from internal speakers while headphones were plugged in. Disconnected headphones, sound came from internal speakers, reconnected phones, sound came from headphones. Let the device go into deep sleep, woke it and played sound - came from internal speakers but was distorted. Deep sleep again, sound now plays from internal speakers with no distortion.
greatgreek said:
Read in another thread that rebooting device with headphones plugged in would resolve this issue - was skeptical but tried it.
It worked for me.
Powered down my TP. Inserted headphones. Powered up and booted into CM9. After boot complete, played sound which came from internal speakers while headphones were plugged in. Disconnected headphones, sound came from internal speakers, reconnected phones, sound came from headphones. Let the device go into deep sleep, woke it and played sound - came from internal speakers but was distorted. Deep sleep again, sound now plays from internal speakers with no distortion.
Click to expand...
Click to collapse
What thread did you find this on? Were you able to use both headphones and speakers after doing this without rebooting?
Not 100% fix
Shortly after discovering the headphone related "fix" for dropping sound, found that it's not 100% of course. Issue came back after prolonged deep sleep.
greatgreek said:
Shortly after discovering the headphone related "fix" for dropping sound, found that it's not 100% of course. Issue came back after prolonged deep sleep.
Click to expand...
Click to collapse
After using the new nightlies I have not had this issue anymore.
ashtrai said:
I made this post in the CM9 thread but I thought Id make a thread here to see if anyone is experiencing the same problem as me.
I've been having a recurring problem with my TP since a while back. My sound stops working when i wake my device up after deepsleep. the only way to get sound working again is to reboot. Installing the bricked-ics kernel fixed this but that kernel was unstable. Ive tried removing android completely from my device, done a webosdoctor and then reinstalling it. Still the same problem. Ive had this since after the 3.5 alpha. im on the latest nightly now.
I've taken some catlogs of when the sound is working after a fresh reboot and one where its not. These catlogs are me pressing on the menu button to try to make a touchsound.
Click to expand...
Click to collapse
I have the same problem since the 0508 or 0507 build...
I have this issue with galaxy s 3
Related
Bit pool????What does it do!
I'll ask this again....by changing the bit pool ....what does this do???? Max bit pool and bit pool????
I have no idea exactly what it does, but I've fiddled with a2dp enough to know that in my experience, turning the bitpool off, or deleting the registry entry greatly reduces skipping while playing music through a bluetooth headset.
WMPlayer to continue playback in standby?
is it possible to get WindowsMediaPlayer on the Diamond to continue playback when in standby? To prevent the screen to drain the battery..even if the light goes off..it still drains unnecessary energy..
The screen turn it off by itself after few seconds and the playback continue. Same goes for the TF3D player. I just wish we had control to skip songs while the screen is off by using the wheel pad.
for me to but I have another problem at once for a song it clipping for a short time its like device has empty buffer for a half a second...clip-clip and continue without problems and only once a song...I have MP3s with different quality from different source so very weird...tried pocketplayer, musicplayer, mortplayer, HTC audioplayer all without preamp or equalizer...
Problem in music palyback in coreplayer?
When I playback music in coreplayer (Audio), when the device goes into suspend mode, it stops playing audio. Is there anyway to keep the music alive, unless I stop it?? I shall be thankful in advance.
46 views but no answer?
[Possible Fix]for Bad Audio in Video Recording
First of all i'd like to thank Meltus and jesus_c and gadgetcheck for their work. http://forum.xda-developers.com/showthread.php?t=1722136 http://forum.xda-developers.com/showpost.php?p=27741216&postcount=54 i merely studied the file, i'm no expert. i just know intermediate stuff. i didn't know what hpf was, so i googled it and found it is high pass filter so i disabled it. that alone didn't do the job well, the rest was educated guess and i'm glad it was right. difference may not be that noticeable on phone speaker but can be clearly noticed when using headset. the experts can now tweak and sort out more stuff after. here's a comparison of vids: old is from default http://www.mediafire.com/?1a0wcd0rdodadd3 new is from tweaked http://www.mediafire.com/?aob456t4qoyz25c attached zip is cwm flashable. UPDATE: vid recording of sgs3 placed on laptop playing music. default BFLB: http://www.mediafire.com/?ke87s5nj2tpfhfb tweaked BFLB: http://www.mediafire.com/?63wzv2jd51bzy6o NEW!!! Default BLG6/8: http://www.mediafire.com/?se4ioy7x4206n1l as you can see, tweaked BLFB and default BLG6/8 are pretty close. the default BFLB's audio in vid was very bad, comparing it to default BLG6/8 there is a marked improvement. samsung has indeed improved audio recording in vids now. default vid starts around 2seconds, the tweaked at 6th second. as can be seen on default, this phone is weak at picking up those between 32hz and 64hz. if you can play the two vids and sync them, you'll see the tweaked picking up more bass than default. app used in sgs3 is rta audio analyzer found in google play.
There is a notable difference between both videos, but as the sound source is just noise it's hard to say if this is a good or bad improvement with naked ear. I will be making some test later with your mod, I hope for the best! Cheers!
i have before and after vids of cars passing by just like gsmarena's. as this was where we all first noticed sgs3's bad audio in vid recording. but sad to say my upload speed here is very slow and the files are over 100mb cos i recorded each over a minute to be sure. all i can say is the vid with tweaked is better. i've listened to both using headset to differentiate well, the tweaked one has more depth which many has complained the audio in sgs3 was lacking. and there is less walkie-talkie effect scratchy noise than before.
You can use VLC to extract the audio channel from the vid files and upload only the audio files. Then you can record 5 minutes on each, and be left with 5mb for each
i used mp4muxer, i extracted the aac audio in raw. default http://www.mediafire.com/?bbcjfj8j6zkmynr tweaked http://www.mediafire.com/?cns7j748i3y2uhj the best way i can describe it is that the mic captures better now. it was windy when i recorded both a while ago, and only the tweaked version as you can hear captured the wind.
radeonxt said: First of all i'd like to thank Meltus and jesus_c and gadgetcheck for their work. http://forum.xda-developers.com/showthread.php?t=1722136 http://forum.xda-developers.com/showpost.php?p=27741216&postcount=54 i merely studied the file, i'm no expert. i just know intermediate stuff. i didn't know what hpf was, so i googled it and found it is high pass filter so i disabled it. that alone didn't do the job well, the rest was educated guess and i'm glad it was right. difference may not be that noticeable on phone speaker but can be clearly noticed when using headset. the experts can now tweak and sort out more stuff after. here's a comparison of vids: old is default http://www.mediafire.com/?1a0wcd0rdodadd3 new is tweaked http://www.mediafire.com/?aob456t4qoyz25c attached zip is cwm flashable. Click to expand... Click to collapse Amazing! This was one of my biggest complaints about video recording with this phone. The dynamic range was cut with a high pass filter and you solved it. Good job and thanks for this!
there is definitely an improvement , but still cant record any bass
Haven't had the chance to experiment but I understand you completely disabled the High Pass Filter by using HPF Switch and set it to 0? { "AIF1ADC1 HPF Switch", 0 }, But another interesting line is the one above it: { "AIF1ADC1 HPF Mode", 2 }, Appearantly there are 3 or 4 modes for the HPF: 0 = Hi-Fi 1 = Voice 1 2 = Voice 2 (3 = Voice 3)? Perhaps setting it to Hi-Fi (value of 0) instead of 1 or 2 (voice) is worth a try as well. I can imagine when the focus is set to voice a lot of surrounding sound is filtered out and Hi-Fi might be more 'general' or 'pure' but without issues of too much noise for the mic? Will try it out some later myself btw
dagrim1 said: Haven't had the chance to experiment but I understand you completely disabled the High Pass Filter by using HPF Switch and set it to 0? { "AIF1ADC1 HPF Switch", 0 }, But another interesting line is the one above it: { "AIF1ADC1 HPF Mode", 2 }, Appearantly there are 3 or 4 modes for the HPF: 0 = Hi-Fi 1 = Voice 1 2 = Voice 2 (3 = Voice 3)? Perhaps setting it to Hi-Fi (value of 0) instead of 1 or 2 (voice) is worth a try as well. I can imagine when the focus is set to voice a lot of surrounding sound is filtered out and Hi-Fi might be more 'general' or 'pure' but without issues of too much noise for the mic? Will try it out some later myself btw Click to expand... Click to collapse I tried setting it to 0 last night. Recording quality was about the same. Something I never noticed before. .. even in the audio recorder, or using an app life tape machine records with no low end bass at all.. .. hell even when recording the bloody radio. ... its a global problem with this phone on all recording levels. .. my sgs 2 does not suffer from this.. . Might be kernel related as all the options I try in this file still do not give me any thing lower then 0.5khz. .. pretty stupid limitation.. ..
it wasn't just hpf that i tried to tweak guys. i did say in first post i didn't know what hpf was, so i googled it and found it is high pass filter so i disabled it. that alone didn't do the job well, the rest was educated guess and i'm glad it was right. difference may not be that noticeable on phone speaker but can be clearly noticed when using headset. just glad that many have confirmed the clarity,volume and such is better. i'm hoping the experts will include tweaking this more along with their other audio recording fixes, since i can do no more further as i've mentioned i'm no expert and also too busy with business these days.
Ugh, yeah... thought I was able to read better Do you know if you have to reboot when changing this conf file? Or is it done on the fly. Might want to play around with it some more.
I've been looking into this recently, you beat me to it This is what I've found (I'm not saying I'm right or anything, these are just my conclusions from research). "AIF1ADC1 HPF" is indeed a High-Pass filter but would disabling the High-Pass filter be a good idea for audio recording? Well, we have no idea what the current cut-off frequency is for the HPF (but we can take an educated guess, see below) and indeed, as 'dagrim1' pointed out, whether the cut-off frequency changes depending on the mode set. I've been unable to find a technical specification of the Galaxy S III's microphone but I'm guessing it wont be very good at handling the lower frequencies. Another reason is the majority of time we want the audio from a video recording it's when we are recording people. The recording of voices certainly wouldn't benefit from the extra bass frequencies that are being recorded from disabling the high-pass filter as the human voice is around 85Hz to 255Hz (including both male and female range - I've chosen this range because it is, roughly, what I was taught. There are people who claim different but it doesn't really matter that much). If we look at the HPF modes (that dagrim1 pointed out), we can see there are 3 modes in use; 0, 1 and 2. Now 1 seems only to be used in the telephony sections ("Communication" modifiers in the file) whilst 2 is used for pretty much everything else (apart from where it isn't used at all, '0'. Although, '0' could itself be another HPF mode and whether it's on or off could be controlled entirely by the switch). The standard Frequency Band used for telephones is, approximately, 300hz to 3400hz (NOTE: this could just be for landline telephones and not mobiles, I'm not entirely sure), so we can logically assume the cut-off frequency of mode 1 is around the 300hz mark. Judging by the fact that telephone frequencies need to be quite heavily limited, I'm guessing that Band 1 will have a lower cut-off point (maybe around 50-100hz or so?), allowing more bass frequencies through. So, you could remove the low-pass filter entirely and capture the whole range of sounds (no idea how the microphone will cope with this as I can't find any technical information about it), you could set it to the standard '2' or you can set the HPF to mode '1', limiting the available frequency range even further but potentially improving the clarity of the recording (it will probably sound tinny as hell too!). That being said, with the 2 recordings 'radeonxt' made, the one with the disabled HPF did sound much better. It could sound worse in certain situations but it could also be an improvement across the board. I see you also added in "AIF1ADC1L Mixer ADC/DMIC Switch". This seems to be a special modifier reserved for In-Call recording. I haven't had much luck adding extra parameters into this file (it seems to be quite strict) but I have no idea whether this will affect the sound or not. In theory, as the microphone on the SGSIII is indeed stereo (I think it is anyway, or am I just making that up?) it could enable both channels if they are not enabled by default. But, if both channels are already used and are simply controlled by 1 HPF and not 2, then this line could just do the same as "AIF1ADC1 HPF Switch". There's also 2 separate sections for the camcorder microphone recording; "built-in mic", the normal one, I'm guessing, and the "back mic". Now I have absolutely no idea what the "back mic" is referring to, unless it means the secondary "noise cancelling mic" but it's not really on the "back" of the device. EDIT: It seems the "back mic" records the right signal and the "built-in mic" records the left. Of course, for any of this to actually be relevant completely depends on whether any of it is actually correct. I guess we'll just have to do some more testing TL;DR version: Does disabling the HPF improve video recording audio? Dunno, lol. Depending upon the situation, perhaps. dagrim1 said: Ugh, yeah... thought I was able to read better Do you know if you have to reboot when changing this conf file? Or is it done on the fly. Might want to play around with it some more. Click to expand... Click to collapse You can either reboot or do "adb killall mediaserver" (or just "killall mediaserver" from a terminal) to re-load all the audio files
Could someone possibly do a recording of pink noise out of studio monitor speakers, so he could then do an analysis of the recorded frequency range? –—–—–—–—–—–—–—–— tapatalked from Galaxy SIII
welcome meltus. yes i didn't even know what the hpf acronym was. i googled just hpf and got many results, so i added what is hpf in audio and the search result yielded this wiki: A high-pass filter (HPF) is an electronic filter that passes high-frequency signals but attenuates (reduces the amplitude of) signals with frequencies lower than the cutoff frequency. The actual amount of attenuation for each frequency varies from filter to filter. A high-pass filter is usually modeled as a linear time-invariant system. It is sometimes called a low-cut filter or bass-cut filter.[1] High-pass filters have many uses, such as blocking DC from circuitry sensitive to non-zero average voltages or RF devices. They can also be used in conjunction with a low-pass filter to make a bandpass filter. was about to search what the hell attenuate means but luckily inside the parenthesis it showed it means reduces. so knowing the basic stuff that 0 would mean disable and 1 would mean enable, i changed it to 0. then after that i tried recording with hpf value changed to 0, i didn't notice much difference. the only time it made a difference like shown in those before,after vids was when i added AIF1ADC1L and AIF1ADC1R on camcorder's built in mic and back mic. i decided to retain the change i made to hpf to 0 since getting a few bass perhaps is better than nothing. since i was just interested with camcorder, i just looked at what was in there. then i saw settings for built in mic and back mic, one was just L the other was R. so i figured one was used for Left and other was used for Right. the aif1adc was simply just aif1adc, i found an aif1adcL and aif1adcR so i tried putting both on built in and back mic because i was thinking builtin mic is the one on the bottom and back mic is the one on top. thank you meltus, i noticed another thing maybe we can try to tweak in those mic settings and it's { "IN1L Volume", 30 }, { "MIXINL IN1L Volume", 0 }, and { "IN1R Volume", 30 }, { "MIXINR IN1R Volume", 0 }, how about we try playing around those and upping those volumes?
dagrim1 said: Ugh, yeah... thought I was able to read better Do you know if you have to reboot when changing this conf file? Or is it done on the fly. Might want to play around with it some more. Click to expand... Click to collapse i use cwm manager and select flash update then select that zip file. so it loads since it restarts after it finishes flashing. its fast since it's only a 197kb zip file.
FadeFx said: Could someone possibly do a recording of pink noise out of studio monitor speakers, so he could then do an analysis of the recorded frequency range? –—–—–—–—–—–—–—–— tapatalked from Galaxy SIII Click to expand... Click to collapse yes, there are many experts and audiophiles here in xda that have the knowledge and the gadgets to do this stuff. i for myself can only use rta audio analyzer which can be found in google play. the number of bands i chose in options is 20 - 1/2 octave. then i played on my laptop black eyed peas let's get it started and place the sgs3 on the laptop's keyboard. the thing i noticed is that 250hz to 16k range all get picked up and can reach about -40db. the weakest pick up is between 32hz and 64hz. my guesswork says the ones on the left side are for bass right? center to right are mid range to high pitches?
radeonxt said: welcome meltus. yes i didn't even know what the hpf acronym was. i googled just hpf and got many results, so i added what is hpf in audio and the search result yielded this wiki: A high-pass filter (HPF) is an electronic filter that passes high-frequency signals but attenuates (reduces the amplitude of) signals with frequencies lower than the cutoff frequency. The actual amount of attenuation for each frequency varies from filter to filter. A high-pass filter is usually modeled as a linear time-invariant system. It is sometimes called a low-cut filter or bass-cut filter.[1] High-pass filters have many uses, such as blocking DC from circuitry sensitive to non-zero average voltages or RF devices. They can also be used in conjunction with a low-pass filter to make a bandpass filter. was about to search what the hell attenuate means but luckily inside the parenthesis it showed it means reduces. so knowing the basic stuff that 0 would mean disable and 1 would mean enable, i changed it to 0. then after that i tried recording with hpf value changed to 0, i didn't notice much difference. the only time it made a difference like shown in those before,after vids was when i added AIF1ADC1L and AIF1ADC1R on camcorder's built in mic and back mic. i decided to retain the change i made to hpf to 0 since getting a few bass perhaps is better than nothing. since i was just interested with camcorder, i just looked at what was in there. then i saw settings for built in mic and back mic, one was just L the other was R. so i figured one was used for Left and other was used for Right. the aif1adc was simply just aif1adc, i found an aif1adcL and aif1adcR so i tried putting both on built in and back mic because i was thinking builtin mic is the one on the bottom and back mic is the one on top. thank you meltus, i noticed another thing maybe we can try to tweak in those mic settings and it's { "IN1L Volume", 30 }, { "MIXINL IN1L Volume", 0 }, and { "IN1R Volume", 30 }, { "MIXINR IN1R Volume", 0 }, how about we try playing around those and upping those volumes? Click to expand... Click to collapse Ah, so it was the "AIF1ADC1L/R" lines that actually made the difference? That's interesting, I wonder what other lines we could add to gain more control? I think that the Volume parameters will simply be microphone gain, so to achieve clearer results we could try lowering that value so the microphone distorts less. Or, the "AIF1ADC1" value could be something to do with the HPF and could perhaps control the cut-off value? There's a lot we don't know, it's a shame Samsung didn't provide us with any documentation about it! I also have a pair of ADAM A7X studio monitors so I'll do the "Pink Noise" testing, as suggested by FadeFx, with those later and see if changing the HPF mode value actually does make any difference.
yes AIF1ADC1L/R that made the difference. can be clearly heard when we use headset.
Meltus said: Ah, so it was the "AIF1ADC1L/R" lines that actually made the difference? That's interesting, I wonder what other lines we could add to gain more control? I think that the Volume parameters will simply be microphone gain, so to achieve clearer results we could try lowering that value so the microphone distorts less. Or, the "AIF1ADC1" value could be something to do with the HPF and could perhaps control the cut-off value? There's a lot we don't know, it's a shame Samsung didn't provide us with any documentation about it! I also have a pair of ADAM A7X studio monitors so I'll do the "Pink Noise" testing, as suggested by FadeFx, with those later and see if changing the HPF mode value actually does make any difference. Click to expand... Click to collapse As for low end recording, Changing AIF1ADC1 to AIF2ADC2 gave me low end roll-off around 200Hz lowest point at -30db was 163Hz. What I did: I recorded a few bass kicks, drops and rumbles from a few VST plugins, put the phone next to my Monitors (and the Sub) - recorded audio/video and then I used the linear frequency graph in Cubase to see what my recorded waveform was doing. This is the Mod I tested : Modifier "Camcorder" { SupportedDevice { "Builtin Mic" } Enable { { "AIF2ADC2 HPF Mode", 0 }, { "AIF2ADC2 HPF Switch", 0 }, { "IN1L Volume", 30 }, { "MIXINL IN1L Volume", 0 }, { "AIF2ADC2 Volume", 96 }, { "AIF2ADC2L Mixer ADC/DMIC Switch", 1 }, { "AIF2ADC2R Mixer ADC/DMIC Switch", 1 }, AND REPEAT FOR THE "BACK MIC" I modded the values in Voice for recorder to match what I had done in Camcorder Modifier. Try it, record bass from a sub and see - I got results (High-end was untouched) EDIT::::::......... This did not do what I thought it was doing. Turns out thaqt Sub frequencys where recorded below 300Hz, but up from 90 to 30Hz - there is a 'Scoop-out' so this didn't really do anything significant. BTW - in AIF2ADC2 the ADC stands for 'A'nalogue to 'D'igital 'C'onverter ... no filter preferences there - but maybe switching it to a different ADC will give 'Full Range' processing???
yes i did try 0'ing or disabling those hpf in the enable parts last night and compared results. wasn't sure since there is no noticeable difference and knowing laptops don't give out good bass as compared to speakers with subs. and yes that's another one who has noticed that, from 32hz it gets better than nothing bass then onwards to 64hz the eq bar of rta audio analyzer for android shows it mostly stays at the bottom most of the time.
[Q] Music randomly stops playing
Sometimes when the network connection changes from H<>3G PowerAmp stops playing my music. The same happens to the stock audio player. I can reproduce this by just turning mobile data on/off but not always. Sometimes it looks like i can not reproduce it anymore until a few minutes later after exploring the settings app a bit it can be reproduced again. It's the same issue as described here. It doesn't matter if earphones are plugged in or not. I have tried to disable certain apps like Google Play but it didn't help. Unfortunately i can not disable every app. Google Play Service for example can not be deactivated. The only way to keep the music playing while i am on the move is to enable flight mode which is a really lame workaround. Is anyone else having this issue? My phone is on stock, unlocked bootloader, with SuperSU and Adaway installed. Not sure if this issue was present before i unlocked the phone but i never saw this before and i was using it a lot for playing music while i am out.
Using superuser with locked bootloader? If you didn't unlock your bootloader you can't have root > having superuser is useless Poweramp: in advanced settings, audio, set buffer to highest level and see if it solves the problem... Same happened to me, and solved by changing poweramp buffer size FCKöln said: Sometimes when the network connection changes from H<>3G PowerAmp stops playing my music. The same happens to the stock audio player. I can reproduce this by just turning mobile data on/off but not always. Sometimes it looks like i can not reproduce it anymore until a few minutes later after exploring the settings app a bit it can be reproduced again. It's the same issue as described here. It doesn't matter if earphones are plugged in or not. I have tried to disable certain apps like Google Play but it didn't help. Unfortunately i can not disable every app. Google Play Service for example can not be deactivated. The only way to keep the music playing while i am on the move is to enable flight mode which is a really lame workaround. Is anyone else having this issue? My phone is on stock, unlocked, with SuperSU and Adaway installed. Not sure if this issue was present before i unlocked the phone but i never saw this before and i was using it a lot for playing music while i am out. Click to expand... Click to collapse
Bootloader is unlocked using htcdev. I only forgot to mention it correctly (fixed now). I have already set the buffer size to 500ms. Everything below 500ms causes audio glitches on this device. Anyway, i tried changing the value without luck. I also enabled the wake locks in the advanced settings but it doesn't help. As i said, it happens with the default music player as well.
It seems that i have figured it out. I had an app called XBMC Music Pump installed which requrests the audio focus everytime something changes on the network. Most likely a bug... already contacted the developers. Code: 10-20 21:31:04.446: I/MediaFocusControl(1152): AudioFocus requestAudioFocus() from [email protected][email protected] 10-20 21:31:04.446: I/MusicPumpXBMC(11233): Successfully requested audio focus