I got Helmi's AKU 3.5 Rom Kitchen to work(NO USB)

[ImCoKeMaN]

Helmi_c,
I'm just about to try both of the files you posted to see how that goes. I see you have a way to check driver resource conflicts. Would it help if i were to post the version of the rom i made with the ms2_usbfn.dll driver that locked up CONSTANTLY, but did begin to activesync? It seemed like a resource conflict since it went away when i took out the membase reg entry, but i dont have the whatever tool it was you used to check for that conflict. I'd love to hear it if you are willing to share and i'd be more than happy to post the broken ROM if it would help.

Thanks for all your help!

[finster869]

OK, I followed Helmi's suggestion and deleted the platformxxx.reg from the cab. Bluetooth now appears to work properly!!!!

GREAT JOB HELMI!!!!

QUESTION: How do we modify the Kitchen so that we can incorporate these revised files right into it rather than having to run the cab afterwards? I see that there is a folder in the OS for these .dll, but I'm not sure how to replace the contents since the folder has several files and not just the .dll. Anyone????

[helmi_c]

Originally Posted by ImCoKeMaN

Helmi_c,
I'm just about to try both of the files you posted to see how that goes. I see you have a way to check driver resource conflicts. Would it help if i were to post the version of the rom i made with the ms2_usbfn.dll driver that locked up CONSTANTLY, but did begin to activesync? It seemed like a resource conflict since it went away when i took out the membase reg entry, but i dont have the whatever tool it was you used to check for that conflict. I'd love to hear it if you are willing to share and i'd be more than happy to post the broken ROM if it would help.

Thanks for all your help!

Do you means Ram Address conflict, I just watch the ram to see the conflicted part, read, calculate, subtract, the ram address of module/dir dll's one by one... yes it pain in the **** part... but hey... I just gettin a bit curious sometimes...

Originally Posted by ImCoKeMaN

Would it help if i were to post the version of the rom i made with the ms2_usbfn.dll driver that locked up CONSTANTLY

well, I'll give it a shot once again if I hv time, not now...
please tell me where to get the rom...

[helmi_c]

Originally Posted by sfaure03

Tells us it is, indeed, a dll conflict problem.

I'm rolling back to 3.3 though.. See if WMP has issues. I've noted that even w/ a headset under 3.5 the first 30 seconds of WMP skips, just like in bluetooth.

if the skipping at first 30 seconds of WMP still exist... try to lower this:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
  "Priority256"=dword:6e

lower value=higher priority
higher value=lower priority

Originally Posted by finster869

OK, I followed Helmi's suggestion and deleted the platformxxx.reg from the cab. Bluetooth now appears to work properly!!!!

GREAT JOB HELMI!!!!

QUESTION: How do we modify the Kitchen so that we can incorporate these revised files right into it rather than having to run the cab afterwards? I see that there is a folder in the OS for these .dll, but I'm not sure how to replace the contents since the folder has several files and not just the .dll. Anyone????

Its safe to replace it... just delete the module dir and replace with the file one...

[ImCoKeMaN]

Wow ok so you basically pay super close attention to the nitty gritty details by hand. That is very admirable! Is it the imaginfo.txt files you look in at the realaddr key? As for the rom, unfortunately i don't have it saved off special at the moment cuz it was broken, but i'll probly end up rebuilding it if this new info doesn't already lead to the solution. Besides i already put my phone in a state where i need to hard reset anyway

[helmi_c]

Originally Posted by ImCoKeMaN

Wow ok so you basically pay super close attention to the nitty gritty details by hand. That is very admirable! Is it the imaginfo.txt files you look in at the realaddr key? As for the rom, unfortunately i don't have it saved off special at the moment cuz it was broken, but i'll probly end up rebuilding it if this new info doesn't already lead to the solution. Besides i already put my phone in a state where i need to hard reset anyway

yes, not all offcourse... just the suspicious one...I'll getting mad if I must check them all... they ussualy hv 300-400 difference modules... sure I'll be bang my head if i must do it all modules...

well, we'll se about that... hopes the new info will lead to solution...

[jeffme]

Originally Posted by sfaure03

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.

ummm... yes, indeed! :P Thanks for the good catch & looking forward to the results of this alpha effort!

[sfaure03]

priority setting on WMP worked perfectly helmi. Thanks.

I'm off to fetch my a2dp headset now. Maybe we just fixed the a2dp skipping as well.

[schettj]

I'm going to try and keep a summery of this topic on the wiki here

http://wiki.ppcgeeks.com/index.php?t...roubleshooting

Feel free to update it, or I will every day or so... Too much good info, and too much to read

[finster869]

Originally Posted by schettj

I'm going to try and keep a summery of this topic on the wiki here

http://wiki.ppcgeeks.com/index.php?t...roubleshooting

Feel free to update it, or I will every day or so... Too much good info, and too much to read

Nice job on the wiki write-up!