Why sound isn't working on the TP2.

[Unknownforce]

Originally Posted by ghost_deini

You can't move the wavdev.dll from your phone(i was trying for almost a day) b/c its part of the execute in place kernel, XIP, of winmo. So I went into the irc and phh told me to google topaz oem drivers. As he is one of the most involved devs I did not question him.

You may not be able to pull it directly from the phone, but you can convert it to a module from the XIP port from within any one of the kitchens for a TP2.

[gface2k]

not sure if this will help but its from the original sprint rom

[proxhack]

Great job gface2K...I am sure this will be very helpful.

[Holyrolla]

Not sure if this will help, but it's just an observation, and maybe it's just my perception.

Whenever my phone sits silent for awhile, and then I do something like...say...bursting the first set of bubbles in Bubble Breaker, it seems as if the sound fades in, as if the sound system was asleep and then woke up.

Is there a subsystem or program that puts the sound to sleep? If so, maybe that's something to look at, how does the sound seemingly fall asleep, and how to wake it up.

[Unknownforce]

I'm sure that that's just part of the power management that isn't implimented yet, but I'm not sure that it will be of any help.

As has been said, it's more that when the processor is called upon to make sound, it doesn't do anything at all. So whether or not we can wake it up or put it back to sleep at this point is irrelevant, we just need to get it to play any sounds at all.

But as always, any and all observations and thoughts are welcomed. Thanks for sharing. I'm slowly learning ARM ASM, and as soon as it starts to "click," I can hopefully figure out some of the dll files and how exactly they interact with the processors and possibly help to write/fix some of the code. or at least provide the real devs with some good info so that they can write the code and adapt what I find with the existing android code.

[variance]

are people still actively working on decompiling the rhodium/topaz drivers?
are they different/do they handle sound differently?
and what specific DLLs am I to focus on.

I'm in the middle of pulling the trigger on outsourcing it to getafreelancer.com to some chinese devs who claim experience with ARM Assembly, developing for mobile platforms/etc. Gonna interview them more thoroughly after I get a better idea of the issue in question. this work they will do will have to be limited to the reverse engineering/decompiling of the .dlls as obviously they won't have the hardware or anything like that to test with.

Want to make sure i'm not duplicating work being done/almost done already.. I'm putting $500 on it for now. although in two months i'll be able to put more $ on the comission. (speaking of which I'm willing to pay that $500 if someone on here manages to to do it and find out what the hang up in the driver is.)

I figure chinese devs have access to resources we don't (in terms of chinese community dev-forums and being able to read white-papers/etc that may be in chinese and not in english.)

so I need to know Do I give them Topaz driver or Rhodium driver?
does anyone know where I can find a comprehensive white paper/documentation of the chipset archictecure for the phone?

I've been playing with the EVO. It would be perfect if it had a hardware keyboard.
sigh. not one decent snapdragon wvga keyboard cdma slider on the horizon.

finally. what is the IRC server and irc channels for this phone and/or the dev efforts?
i found this log page. but is this the most active channel?
http://irclog.netripper.com/?chan=ht...month=5&day=20

[[ACL]]

Originally Posted by variance

are people still actively working on decompiling the rhodium/topaz drivers?
are they different/do they handle sound differently?
and what specific DLLs am I to focus on.

I'm in the middle of pulling the trigger on outsourcing it to getafreelancer.com to some chinese devs who claim experience with ARM Assembly, developing for mobile platforms/etc. Gonna interview them more thoroughly after I get a better idea of the issue in question. this work they will do will have to be limited to the reverse engineering/decompiling of the .dlls as obviously they won't have the hardware or anything like that to test with.

Want to make sure i'm not duplicating work being done/almost done already.. I'm putting $500 on it for now. although in two months i'll be able to put more $ on the comission. (speaking of which I'm willing to pay that $500 if someone on here manages to to do it and find out what the hang up in the driver is.)

I figure chinese devs have access to resources we don't (in terms of chinese community dev-forums and being able to read white-papers/etc that may be in chinese and not in english.)

so I need to know Do I give them Topaz driver or Rhodium driver?
does anyone know where I can find a comprehensive white paper/documentation of the chipset archictecure for the phone?

I've been playing with the EVO. It would be perfect if it had a hardware keyboard.
sigh. not one decent snapdragon wvga keyboard cdma slider on the horizon.

finally. what is the IRC server and irc channels for this phone and/or the dev efforts?
i found this log page. but is this the most active channel?
http://irclog.netripper.com/?chan=ht...month=5&day=20

Yes, that is the most active channel.

Pay chinese devs ? or pay chinese htc employees who wanna make a quick buck? :-p

ALso have you guys looked into the win dmesg ? there is tons of crap logged when the phone boots.

edit: here is the dmesg from a rhod400 http://pastebin.com/M1Ad4YMv

[variance]

Originally Posted by [ACL]

Yes, that is the most active channel.

Pay chinese devs ? or pay chinese htc employees who wanna make a quick buck? :-p

ALso have you guys looked into the win dmesg ? there is tons of crap logged when the phone boots.

edit: here is the dmesg from a rhod400 http://pastebin.com/M1Ad4YMv

lol. if these chinese devs claim to have experience with qualcomm chipsets and HTC phones in particular. who am I to question that coincidence.

plausibly they could just be a group of middle-class chinese nerd enthusiasts like us who have the benefit of reading documentation on the chipsets that happen to only be in chinese.

anyway after spending some hours reading the logs. short of the xda-dev thread (Link: http://forum.xda-developers.com/show...=671998&page=3 ) where someone was willing to tear apart/break his TP2 to do some hardware tracing/diagnostics on the system board itself.

Originally Posted by BinaryDroid

I'm willing to kill my touch pro 2 and remove the CPU to trace the JTAG locations but I only have the datasheet from the MSM7200/7500, not sure if it will be the same locations. I bet if I hooked up my Segger I could see exactly what is failing on the OpenGL and sound side since alot of hardware debugging is done this way...just sucks I dont know for sure if the pinouts are the same. I'm done it on quite a few different phones and boards over the years so its not a big deal. Omap3430 was simple to trace and the OMAP3530 had the exact pinouts.

pending what the diagnostics/tracing discovers. I'll hold off on the hiring. might give me more details to add into project goal description.

[[ACL]]

Originally Posted by variance

anyway after spending some hours reading the logs. short of the xda-dev thread (Link: http://forum.xda-developers.com/show...=671998&page=3 ) where someone was willing to tear apart/break his TP2 to do some hardware tracing/diagnostics on the system board itself.


pending what the diagnostics/tracing discovers. I'll hold off on the hiring. might give me more details to add into project goal description.

Yea. I'm on that thread as well waiting for results. I'm actually salivating just thinking of the possibilities ..

[variance]

Please. let me know of some of these possibilities
I've been hoping the TP2 running android with sound reasonbly fast would be all I need to hold me over.

because Im being tempted with a free HTC evo right now.
and I'm playing with it.
but I realllly like my SERO plan.
and having a hardware keyboard.

but it's tempting me towards the darkside.