In keeping with the awesome work on gps development here is a thread dedicated to audio development.
We're going to get the audio changes pushed to the sourceforge git today.
Before pushing changes back to the git, make sure they're tested
Until we get them onto sourceforge you can find them here.
Again. please DO NOT push any changes to here without checking with Vilord as we're going to be moving them to sourceforge.
http://code.google.com/p/vogue-android/source/list
Things that need to be looked over are audio routing for bluetooth
And here is the most recent Audio libs, these are for eclair and 2.1 only.
If you like my work and would like to donate me a beer you can by clicking here Beer Me
I'm merely a layman, but is this the groundwork for AD2P? (bluetooth stereo headphones)
This is getting crazy...You guys are on fire!!! This is about the only forum I've been on where there are more experts than n00bs like myself
I don't know what's required, but we should really be moving this Audio stuff to the kernel using ALSA.
Then we can use the already-maintained AndroidALSA drivers. And the BlueZ bluetooth drivers....
Less to debug that way... and we don't have to go through this with every android version.
I added the link
Hi mssmison,
Great work! I'm working on porting OpenEclair for Kaiser/Vogue/Polaris. Often I get a ton of these errors:
Code:
W/AudioTrack( 134): obtainBuffer timed out (is the CPU pegged?)
When I kill the mediaserver process and let it restart it fixes itself.
I'm not sure if this problem comes from the audio driver or the kernel, but it happens most often directly after the boot animation -- I'm guessing because that's when CPU use is the highest?
I checked dmseg for relevant errors, and here's what I found that might help:
Code:
[ 89.820245] audmgr_enable: enabled
[ 89.820287] audmgr: unexpected state 2 while enabling?!
...
[ 89.821702] rpc_write(5,0,2,3000000a,0,1,0,0,0,0,1,0,2,4,)
[ 89.821840] e,0,2,31000002,0,3,0,0,0,0,3,0,0,)
[ 89.821964] [RR] ERROR no local ept for prog 02000031 replying anyway!!
[ 89.821994] rpc_write(e,1,0,0,0,0,)
[ 89.823040] rpc_read_reply(5,1,0)
[ 89.823102] adsp: module AUDPPTASK has been registered
[ 89.823160] msm_adsp_enable() 'AUDPPTASK'
[ 89.823197] rpc_write(6,0,2,3000000a,0,1,0,0,0,0,1,1,2,4,)
[ 89.824114] rpc_read_reply(6,1,0)
[ 90.780193] adsp: module 'AUDPPTASK' enable timed out
[ 90.780278] adsp: module AUDPPTASK not enabled before write
[ 90.780313] adsp: module AUDPPTASK not enabled before write
[ 90.780343] adsp: module AUDPPTASK not enabled before write
[ 90.780373] adsp: module AUDPPTASK not enabled before write
[ 90.780399] adsp: module AUDPPTASK not enabled before write
[ 90.780429] adsp: module AUDPPTASK not enabled before write
[ 90.781509] audio_ioctl 40046100
[ 90.781564] audio_enable()
[ 90.782978] audio_disable()
[ 90.783043] 7200 Audio: Idle: using speaker.
[ 90.783101] snd_set_device 1 1 1
[ 90.783139] rpc_write(7,0,2,30000002,0,1,0,0,0,0,1,1,1,3,0,)
[ 90.784098] rpc_read_command(f,0,2,31000002,0,3,0,0,0,0,3,0,0,)
[ 90.784258] [RR] ERROR no local ept for prog 02000031 replying anyway!!
[ 90.784293] rpc_write(f,1,0,0,0,0,)
[ 90.784411] rpc_read_reply(7,1,0)
[ 90.784453] adsp: module AUDPPTASK not enabled before write
[ 90.784539] audmgr_disable
[ 90.784571] rpc_write(8,0,2,30000013,0,2,0,0,0,0,0,)
[ 90.785671] rpc_read_reply(8,1,0)
[ 90.785703] audmgr_disable: wait for disable
[ 90.816656] rpc_read_command(10,0,2,31000013,0,1,0,0,0,0,1,6,1,30,59e870,)
[ 90.816893] audmgr: DISABLED
[ 90.816941] rpc_write(10,1,0,0,0,0,)
[ 90.817034] audmgr_disable: disabled
[ 90.817084] audpp: disable
[ 90.817111] msm_adsp_disable() 'AUDPPTASK'
[ 90.817163] rpc_write(9,0,2,3000000a,0,1,0,0,0,0,1,2,2,4,)
[ 90.818864] rpc_read_reply(9,1,0)
[ 90.818943] adsp: closing module AUDPPTASK
[ 90.818998] adsp: disable interrupt
...
After that I killed the mediaserver process and let it restart. The only errors I see after that are these:
Code:
[ 162.450120] adsp: waiting for DSP write ready
[ 162.450120] audio_ioctl 40046100
[ 162.450120] audio_enable()
[ 163.040122] audpp: DMA missed
[ 163.040122] audpp: DMA missed
[ 163.052852] audpp: DMA missed
[ 163.070122] audpp: DMA missed
...
The precompiled libs work great. Any tips on getting them to compile on the latest aosp?
Sorry for stiupid question. I'm new in Android.
How to "install" those files at device?
Didn't know this thread existed. So, will this get BT Audio working on Eclair builds?
Dukenukemx said:
Didn't know this thread existed. So, will this get BT Audio working on Eclair builds?
Click to expand...
Click to collapse
I used this libs on myn's Warm Eclair Beta 2 and still no BT audio routing, so I guess the answer is "no". :/
I'm waiting for BT fix too. Not a developer so can't help much with the developing part, but I can help with testing if need occurs.
I'm waiting for BT fix to. Also not a developer but can help with testing if needed.
if anyone is looking to get BTaudio working...
check out polymod 2.1g with the BT&Wifi update. (for kaiser anyway)
it has been the only eclair that my BT headset works on.
I tried to use the update on 2.1d (which is a faster build) but no more BTaudio.
I have also tried on other builds with no success.
just for the fun of it, I went back and re-installed 2.1g+updates this afternoon and
it still works with latest nbh.
I worked on this for countless hours comparing the diff between 2.1g and 2.1d but I cant get anywhere with it.
maybe someone with more android experiance could check it out.
It's a real shame that Poly couldn't fix his Kaiser. He did post recently in the Vogue kernel thread about his Kaiser problem, but he still couldn't fix it. Since he got BT audio working in Eclair, someone could try asking him how he did it.
on a postive note...
this means that the BTaudio issue is not kernel related
and should be an easy fix once polys secret is discovered.
I have a few more development hurdles to overcome before I can attempt to
assist in any of these issues. but If nobody has addressed them by then I will
be sure to get on it.
mnjm9b said:
if anyone is looking to get BTaudio working...
check out polymod 2.1g with the BT&Wifi update. (for kaiser anyway)
Click to expand...
Click to collapse
Can you please post polymod 2.1 g BT Update I can't find it anywhere.
Millence said:
Can you please post polymod 2.1 g BT Update I can't find it anywhere.
Click to expand...
Click to collapse
here.
I think this is it. I have the file on my backup drive.
if this one doesn't work, let me know and I will upload mine.
Thanks!
Instaling right now!
Dukenukemx said:
It's a real shame that Poly couldn't fix his Kaiser. He did post recently in the Vogue kernel thread about his Kaiser problem, but he still couldn't fix it. Since he got BT audio working in Eclair, someone could try asking him how he did it.
Click to expand...
Click to collapse
Try copying your /system/libs folder from working bt audio polymod build into an androidupdate.tar, and applying it to another elair build
*M* said:
Try copying your /system/libs folder from working bt audio polymod build into an androidupdate.tar, and applying it to another elair build
Click to expand...
Click to collapse
Oh.. I wish it was that easy.
I think that was the first thing I did when poly's 2.1d came out.
I also did that with other builds as well.
mnjm9b said:
here.
I think this is it. I have the file on my backup drive.
if this one doesn't work, let me know and I will upload mine.
Click to expand...
Click to collapse
Doing a diff on this update. It contains wlan.ko libs which appears to be for the wireless lan.
The sysinit.rc changes which touch the BlueTooth references are identical to what we have in our latest Eclair Builds (SuperEclair and Warm Eclair). It appears poly's previous build was referencing bluetooth differently and he needed a fix.
With that said, I would be shocked if this fixes our BT Audio on vogue.
I got a bt headset today. It works fine on donut, tried out polymod, it pairs and connects and says its routing media to the headset but still goes through the phone. Perhaps the code is kaiser specific
Ok so this is driving me up the walls.
I got this new secondhand ( ) 3T, which had some ROM issues: on startup of the stock Oreo rom Dirac Control would repeatedly crash forcing the device to factory reset and reboot.
So I figured the issue was a bad flash by the previous owner, however I've went through a zillion roms so far without getting the phone working as it should. That is, everything works except sound and things depending on sound. Seeing this is a phone sound is kinda crucial
My expectation has been so far that it still is somehow a software issue, as an hardware issue that (outwardly) /only/ breaks sound is too odd for me (sound controller is wihtin soc).
Things I've done:
-Went back to nougat following the guides that are on this forum.
-went to lineageOS
-reflashed phone using OEM unbrick tools in Windows (MSM program), twice (both versions that could be had on the web)
-went fully OEM lock stock and flashed all the way up to Oreo using OEM updates
I suspect that somehow audio depends on a special partition which has become botched by flashing done by the previous owner. Are there any partitions that relate to the audio functions where the SOC loads some special firmware from?
Perhaps some of the data on the ESF partitions relates to the audio functions?
Anyone has any ideas or suggestions?
Attached to this post you will find for your debugging pleasures a logcat dump of me turning on the phone and turning it off again. It is quite noisy, so 1,5 meg in size uncompressed.
-update bumb-
Running OOS A3003_28_161027 build the following appears in dmesg:
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt1-mv property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt2-mv property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt3-mv property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias1-cfilt-sel property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias2-cfilt-sel property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias3-cfilt-sel property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias4-cfilt-sel property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-dmic-clk-drv-strength property in node /soc/[email protected]/tasha_codec failed, err = -22
wcd9335-slim tasha-slim-pgd: wcd9xxx_slim_probe: codec type is 2
[ 5.170191]@3 IPC_RTR: ipc_router_create_log_ctx: Unable to create IPC logging for [mpss_IPCRTR]
[ 5.470344]@0 wcd9xxx_slim_probe: failed to get slimbus tasha-slim-pgd logical address: -6
[19700125_14:14:44.584697]@0 init: Unable to open persistent property directory "/data/property": No such file or directory
[19700125_14:14:44.647916]@0 init: cannot find '/system/bin/ptt_socket_app', disabling 'ptt_socket_app'
[19700125_14:14:44.647953]@0 init: cannot find '/system/bin/usb_uicc_client', disabling 'usb_uicc_daemon'
[19700125_14:14:44.654408]@0 init: cannot find '/system/xbin/perfprofd', disabling 'perfprofd'
[19700125_14:14:44.740997]@2 init: cannot find '/system/vendor/bin/seemp_healthd', disabling 'seemp_healthd'
[19700125_14:14:44.760620]@2 init: cannot find '/system/vendor/bin/qvrservice', disabling 'qvrd'
[19700125_14:14:44.760650]@2 init: cannot find '/system/bin/secotad', disabling 'secotad'
[19700125_14:14:44.768017]@2 init: cannot find '/system/bin/dts_configurator', disabling 'dts_configurator'
[19700125_14:14:45.545454]@0 wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-ldoh-v property in node /soc/[email protected]/tasha_codec failed
wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-dmic-clk-drv-strength property in node /soc/[email protected]/tasha_codec failed, err = -22
Click to expand...
Click to collapse
So it seems there are a few system bins (and maybe firmware???) missing. Though these might also just normaly not be there. Also it seems the SOC communicates with audio chip using I2C, but does not seem to be able to enumerate the device normally, which would point to either hardware failure or missing firmware/otherbinaryblobs.
I have flashed using the 'official' unbrick tool, so I would assume all data is correctly flashed onto the phone, and by that I would normally exclude missing firmwares and such as a cause of the issues.
Is there anybody here that can shed more light onto this?
-edit-
More information: normally the phone fires some events when jacks get plugged in, these are also absent. I'm planning on dissasembling the phone and cleaning everything out with alcohol, just to be sure.
Though if it is a software issue it would be nicer to keep it closed.
You having flashed with the unbrick tool, and I assume the full update zip (>1.5 GB) to get the "fully stock", would lead me to believe it is a hardware problem. Both of those methods should have properly flashed the firmware.
redpoint73 said:
You having flashed with the unbrick tool, and I assume the full update zip (>1.5 GB) to get the "fully stock", would lead me to believe it is a hardware problem. Both of those methods should have properly flashed the firmware.
Click to expand...
Click to collapse
Yes, either hardware failure or firmware files that are not included in the unbrick tool (like those resting on ESF partitions)
Doing a search on Dirac control service stopped yields quite a few results of people sharing the same problem, and for who also a downgrade to nougat did not solve the issue. They seem to have needed a motherboard swap
So either the Oreo upgrade causes hardware issues in some cases, but not all, or the Oreo update messes up some firmware files in some cases but not all.
Had same problem on my OP3. Only thing which worked was downgrading to android 6.0.1
So the audio is working like a charm on 6.0.1 except the headphone jack, when I plug in headphones i dont get the headphone logo on top and the sound plays through BOTH headphones and the speaker
fizzk11 said:
So the audio is working like a charm on 6.0.1 except the headphone jack, when I plug in headphones i dont get the headphone logo on top and the sound plays through BOTH headphones and the speaker
Click to expand...
Click to collapse
You can workaround that using an app like SoundAbout, which can force playing audio on specific route
Okay so the problem is back after a day. This happened to me in the past, phone works perfectly fine for a while after flashing a rom or factory resetting, then out of the blue, using the microphone crashes the phone and problem is back. Really makes me think this is a software issue
Did the problem fixed? I have same issues. Please help??
Hi guys, same problem here, after repairing this OP3T the phone was working great when suddenly, the sound stopped working, i have no sound through ear, loud speaker, jack 3.5 neither... i replaced the loud speaker module thinking it was broken but nope, the problem persist... I´m on Oxygen OS with nougat.
Hey, I'm sorry to post on such an old thread but did you manage to find a solution? I'm pretty much facing the same issues.