|
||||
USB driver update
I was looking at other OEM packages that seem to reference the USB and or the same memory area that was causing problems with the ms2_usbfn.dll package and it looks like the ohci.dll package may be related/conflicting. There are reg entries in there for QCT1.DLL, but the package builds a QCT.dll. This piqued by curiosity so i decided to rename the reg entry to the actual DLL name.
After flashing a rom with this change a USB connection was made, but it wasn't for activesync. It pops up "composite USB Device" in the found new hardware bubble then, "HTC Diagnostic Interface (PID 0B03)" and asks for the qcmdmxp.sys driver on my PC. So i am pretty sure this isn't gonna help too much with the active sync as it's not the usbfn driver, but it was nice have windows at least recognize that i connected a device. |
|
||||
Sounds as though it's treating as if you were in diagnostic mode?
http://www.ppc6700users.com/forums/v...ic.php?p=20335 Thanks to schettj for the reference links in original thread: http://ppcgeeks.com/low-level-radio-...new-t2276.html |
|
||||
Yeah, that's basically what the reg change did. I put it back though. For anyone who wants to try to figure this out or see what changes i'm currently making the nk.nbf for the rom i'm currently running to troubleshoot the USB issues is here:
ftp://up.ppcgeeks.com/Apache/ImCoKeM...ing_nk.nbf.zip For anyone less bandwidth inclined: Basically I added a usbfndrv.dll and made a few reg changes to use it. It still isn't running the USB, but seems just as stable (except i can't get schettj's sprintOEM package to work properly) |
|
||||
we still more alpha on this 3.5 rom thread jeff..
I think you're refering to colonels beta 3 rom, and he's right now fighting an issue on beta 3. I'd stick w/ beta 2 till colonel starts the new thread on beta 3.
__________________
shawn
|
|
||||
try this patched file cab... it suppose to fix the bluetooth problem... I dont know if it help the usb stuff also, and I dont know if it will effect ur device sounds or not... u guys do the testing..
ftp://ppcgeeks:ezupload@up.ppcgeeks....atch1_test.zip edit: platformxxx.reg is removed with this cab ftp://ppcgeeks:ezupload@up.ppcgeeks....tch1_fixed.zip |
|
||||
helmi_c
Not so much. Its actually worse in that now if I access the connection settings in any way, the ppc locks up complety. However for the first time on 3.5 I know see that if I plug in the USB cable the XP-laptop actually tries to get an ip address for an active sync connection. However at that time it ALSO locks up the PPC, so no address is given out. So. This is the right area. We were having significant problems w/ the Bluetooth screens not working right, and having very long delays and then unsuccessful attempts to enable / disable. However from a practical point of view, its not so good. snicker. You think maybe the registry entries need adjusting? By the way I used a build straight from IMCokeman here, no mods whatsoever from what he has on our ftp site. just a build, hard reset. hard reset again for "good measure", install cab. Soft reset (forced by the cab install). then attempt usb, or bluenet adjustments. Either of which fail. By the way another "interesting" side effect is that whereas the wireless today plugin was showing "sprintpcs" before installing the cab, after the cab, it only shows "Home Service". Seems that maybe some function call is returning "wierd" to the pluggin |
|
||||
Quote:
What happens if you put the phone in flight mode, soft reset while in flight mode, then try to make a usb connection? The reason I ask, is that doing so resolved the "unable to obtain ip address" problem in 3.3 kitchen for me. |
|
|
|