Re: Why sound isn't working on the TP2.
 

First off I would like to thank everyone who is working to give us sound on the Rhodium. I have a vzw Rhod500 and I also have the same audio problem with the stock vzw rom that was released in June. Here is what happened to me. oh btw I'm using BLAZIN froyo released 8/18/2010 not sure which kernal image he's using on that. maybe the August 2nd release. Anyway
I booted android and plugged in my 3.5mm headphones no auido. Then I shut down android and returned to wm and tried to play some music and guess what? no audio. I had to unplug headset and reset the device. Then I had audio again. Went into my media player to play some music and I had sound plugged in headset and still had sound. While the music was playing I started android the music stopped as soon as it launched and then while the os was loading I heard a little pop in my headset. Started android again and tried to play music nothing. Unplugged headset and shutdown android. WM loaded and sound works. I don't know if that will help anyone but there you have it. If I have headset plugged in while wm boots then there is no audio. I bet this affects all the ROMs. Maybe someone with more knowledge should give HTC support a call and see if they can get any info from them which might help figure things out. I for one can't wait for sound on android I hope one of you guys cracks it soon. Keep up the good work.

Something else I noticed there is a delay between the time you plug in the head set and music changes from external speaker to headset.

Re: Why sound isn't working on the TP2.
 

The Touch Pro 1 from Sprint also came with this. Mine is @ home. I am @ work for another 7 hours or I would jump on it.

SIDE NOTE: MUCH PROPS to those of you who are working endlessly to resolve this issue. Don't give up. The answer has got to come soon. I will likely have my Evo 4g by the time it does but I will still be keeping up with the progress & rooting for a fully functional Android on my long time friend, the Rhodium ; -)

Re: Why sound isn't working on the TP2.
 

I found mine last night, it doesn't make a difference in sound. I started thinking, since the usb is only being used for debugging we wouldn't get any audio.

Re: Why sound isn't working on the TP2.
 

even tho no sounds comes thru is it possible that android "thinks" something is plugged in already? If that is the case, plugging in the headset is not going to do anything because the port is already allocated to something else... Right?

Re: Why sound isn't working on the TP2.
 

Not that i dont appreciate the support.. but a lot of these posts dont make any sense.

I'd like to keep this thread going for Dev as much as possible. Once we begin drifting away its just going to balloon up into a mess that no one will want to read.

I think that headphone theory has been beaten to death already ..

Re: Why sound isn't working on the TP2.
 

hey [ACL]

i was helping a friend install android on his HTC HD2 and i saw that they require to run an exe file prior to booting haret in order to get sound working, not sure if you have come across it or seen it before, here's the file if you wana look at it. i ran it on my tp2 before haret but sadly no sound :(

Re: Why sound isn't working on the TP2.
 

yup.. we know all about it. Nope its no help..lol.. sorry we are actually in good communications with the hd2 guys swapping ideas on the irc channel.

Re: Why sound isn't working on the TP2.
 

Jonpry: fixed rpc on the nand version.. i looked into snd.c for the calls you mentioned to enable incall sound Looks like we already make the calls for the device and volume.

1. [ 110.704772] SMD: ch 0 OPENING -> OPENED
2. [ 126.494842] Creating a master local ept d4c3ed20
3. [ 126.515441] snd_ioctl set_device: device 1
4. [ 126.536682] Turnin mic bias on 1
5. [ 126.556945] snd_set_device 1 1 0
6. [ 126.577056] [RPC] CALL on ept d4c3ed20 to 30000002:aa2b1a44 @ 0:00000001 (60 bytes) (xid 2 proc 2)
7. [ 126.613983] [RPC] READ on ept d4c3ed20
8. [ 126.634185] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:d4c3ed20
9. [ 126.673919] [RPC] READ on ept d4c3ed20 (24 bytes)
10. [ 126.697967] buggy program ApmCommandThrea is calling snd_set_volume with dev=256 != 0x11
11. [ 126.735961] snd_set_volume 17 0 5
12. [ 126.757080] [RPC] CALL on ept d4c3ed20 to 30000002:aa2b1a44 @ 0:00000001 (60 bytes) (xid 3 proc 3)
13. [ 126.795349] [RPC] READ on ept d4c3ed20
14. [ 126.801757] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:d4c3ed20
15. [ 126.817260] [RPC] READ on ept d4c3ed20 (24 bytes)

They show no errors. Any other ideas? we are tracing the dlls down but anything that comes to mind might help..

Re: Why sound isn't working on the TP2.
 

Just to clear up any confusion from [ACL]'s statement here- THERE IS NO SOUND EVEN FROM THE HEADPHONE JACK ON CDMA MODELS. When they list headset sound working, they are referring to phone calls, not sound from the OS, if I am not mistaken. It seems that quite a few people are making that mistake now.

If audio worked through the headphone jack, there would be a LOT more discussion on that topic, not to mention we'd very likely be much closer to making this work. But alas, if you read the first post on this thread you will see that the problem is clearly explained as getting the sound processor to respond to any commands at all.

That is all.

Re: Why sound isn't working on the TP2.
 

First of all, I want to thank all of the people working on this.

I just noticed yesterday that I was listening to music on the WinMo side with my USB headset, and booted into Froyo a couple of things happened.

As Android is coming up I could hear a brief (1 second) clicking on the headset.

I could make a phone call and I would get the audio into the headset, but the person on the other end could not hear me.

If I unplugged my headset while in the call, the handset speaker turned on and I could hear the other party, but the other party still could not hear me (maybe the microphone had been turned off when the USB headset is plugged in?)

When I stopped the call, plugging in and unplugging the USB headset gave me a "click" on the headset.

I don't know if this means anything at all, I'm just reporting an experience that I don't recall seeing in the forum before.

The part that has me baffled is the fact that the microphone was disabled for both the headset and the handset.

Anyway, I'll be happy to do any other testing that anyone needs.

By the way my phone is a Rhod400 on US Cellular.