Why sound isn't working on the TP2.

[Unknownforce]

Originally Posted by [ACL]

Nope. i havent tried anything on sound. Jonpry and Phh on xda are the ones i know who were working on it last.

Begin the fundraiser to buy devs ..lol

I'd definitely donate to this cause.

[justinxtreme]

Well my first poss and well um My guess is the new extUSB thing is a part of the problem. I think it requires a special driver to detect if video and audio is also being outputted to the new extusb thus this is the reason USB is charging only for now and audio is not there as all three are connected and when the extusb doesn't send a response to it's status their is no response . Either way decompiling is likely required.
I may be wrong but that's just my point of view. Do the other htc phones that have fully working audio have an extusb port?

[gface2k]

interesting stuff, so the sound system should be working but its not because of an unknown variable. I like the extUSB theory, I guess I'll focus on gathering info on the usb system.

[justinxtreme]

How do I decompile a Windows driver. I'm just a starter and I want to get into this stuff . I have plenty of time in my hands just need some more information.

I was wondering if you guys can use the G1's driver. I was doing some researc and found resemblance wit the processor/graphics chip it has (MSM7201 which is I think on the GSM versions of the TP2) and both are ARM9 architecture and allow te use of complex and extended propietary instructions and signals. The G1 features a extUSB port... and of course likely reports to the whole QSD thing to tell it's status and process sound.
Another phone is the HTC Droid Eris which also features the MSM7600 that is on te CDMA versions of the Touch Pro 2. Also features a extUSB thing. Is it possible to get the driver for audio off the Droid Eris or G1 and port it to the Touch Pro 2..... since they basically use the same processors (CPU/GPU/ and Multimedia-wise) (More notes below) and feature the extUSB..... it's basically porting the same thing over ......

I may be wrong though but it's just a suggestion since I thought that extUSB really has something to do with it.... maybe the developers just overlooked it or something (no offense).

I heard the MSM7200 and the MSM7201 have some key differences. 45nm nand shrink for MSM7201 and the oter one is technically just produced by Broadcom (older nand shrink techniques but same ARM9 architecture) and was seperated numerically for legal purposes. All in all they use the same ARM9 architecture. MSM7200 on TP2 and MSM7201 on G1.

MSM7600 in Droid Eris and Touch Pro 2 CDMA are exactly the same. Well from what I've researched that is

Thanks for all the developer's efforts to making Android on TP2 possible

[variance]

Originally Posted by justinxtreme

How do I decompile a Windows driver. I'm just a starter and I want to get into this stuff . I have plenty of time in my hands just need some more information.

I was wondering if you guys can use the G1's driver. I was doing some researc and found resemblance wit the processor/graphics chip it has (MSM7201 which is I think on the GSM versions of the TP2) and both are ARM9 architecture and allow te use of complex and extended propietary instructions and signals. The G1 features a extUSB port... and of course likely reports to the whole QSD thing to tell it's status and process sound.
Another phone is the HTC Droid Eris which also features the MSM7600 that is on te CDMA versions of the Touch Pro 2. Also features a extUSB thing. Is it possible to get the driver for audio off the Droid Eris or G1 and port it to the Touch Pro 2..... since they basically use the same processors (CPU/GPU/ and Multimedia-wise) (More notes below) and feature the extUSB..... it's basically porting the same thing over ......

I may be wrong though but it's just a suggestion since I thought that extUSB really has something to do with it.... maybe the developers just overlooked it or something (no offense).

I heard the MSM7200 and the MSM7201 have some key differences. 45nm nand shrink for MSM7201 and the oter one is technically just produced by Broadcom (older nand shrink techniques but same ARM9 architecture) and was seperated numerically for legal purposes. All in all they use the same ARM9 architecture. MSM7200 on TP2 and MSM7201 on G1.

MSM7600 in Droid Eris and Touch Pro 2 CDMA are exactly the same. Well from what I've researched that is

Thanks for all the developer's efforts to making Android on TP2 possible

just because teh chipsets are the same doesnt mean shit is initialized or that I/O between the processors/coprocessor/sound chipset is the same. please read and re-read OP explanation.

furthermore. Sound is working on TP1 which has extusb and similar chipset so there goes that explanation.

so far they've come to the conclusion that the only way to know for sure. without making wild guesses would either be the hardware debugging (which someone on xda is doing) and/or decompiling the windows drivers
to see exactly how windows initializes the sound for use.

I highly doubt it's extusb though given all the other extusb winmo phones that work just fine with android and have sound.

[pringlet]

Brainstorming..

One of the differences regarding sound output between the TP1 and TP2 is the TP2 has a 3.5mm jack. Maybe the issue has to do with whatever IC routes the sound to either the 3.5mm jack or the speaker.

pt

[sovereignty03]

Originally Posted by pringlet

Brainstorming..

One of the differences regarding sound output between the TP1 and TP2 is the TP2 has a 3.5mm jack. Maybe the issue has to do with whatever IC routes the sound to either the 3.5mm jack or the speaker.

pt

Good thought...I have a Tilt 2 (a variant of the Rhodium/TP2 family) from AT&T and is does not have a 3.5mm audio jack. But, with that being said, I don't know if the functionality is actually there and they (HTC/AT&T) just decided not to include a jack, or if the functionality was completely deleted from the PCB/Kernel...

[[ACL]]

Originally Posted by variance

so far they've come to the conclusion that the only way to know for sure. without making wild guesses would either be the hardware debugging (which someone on xda is doing) and/or decompiling the windows drivers
to see exactly how windows initializes the sound for use.

You can also trace calls in haret. I'm doing that now for the 3d. Requires a lot of patience.

For those of you who haven't started playing with haret. What are you waiting for ?

[variance]

Originally Posted by [ACL]

You can also trace calls in haret. I'm doing that now for the 3d. Requires a lot of patience.

For those of you who haven't started playing with haret. What are you waiting for ?

+1 on playing with haret.

and respect for having the patience..
after a few hours of tracing calls, my add kicked in as I started trying to think of a way to write a program to automatically do it for me. then I forgot about that when I saw a post of someone who posted up some builds of Froyo on xda that he was requesting someone test with rhodium.. which i'm trying to do now.


TP2 would have made a much better android device.

[sovereignty03]

Originally Posted by justinxtreme

...The G1 features a extUSB port... and of course likely reports to the whole QSD thing to tell it's status and process sound.
Another phone is the HTC Droid Eris which also features the MSM7600 that is on te CDMA versions of the Touch Pro 2. Also features a extUSB thing. Is it possible to get the driver for audio off the Droid Eris or G1 and port it to the Touch Pro 2..... since they basically use the same processors (CPU/GPU/ and Multimedia-wise) (More notes below) and feature the extUSB..... it's basically porting the same thing over ......

I may be wrong though but it's just a suggestion since I thought that extUSB really has something to do with it....

extUSB is just a modified miniUSB that includes analog audio pinouts. If the data can't be read on regular USB or miniUSB, then it can't be read on extUSB...one can actually plug in a miniUSB cable into the extUSB jack and get all the same USB functions (just be careful 'cause the extUSB jack is delicate)...