Quote:
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.
Quote:
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.