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

[eyeballz]

Find out and flash it. Its the weekend. Not a better time for most

[eyeballz]

It looks as though your correct finster


Bluetooth is not working with voice command correctly. If you dont install voice command it works out of the box with voicedialing app from cyberon.

Any quick fixes in the registry to fix this.??

[Alwaysbelieve1]

Originally Posted by eyeballz

Find out and flash it. Its the weekend. Not a better time for most

I don't have time because I'm busy this weekend. I would appreciate a brief rundown please.

[sfaure03]

Me thinks this thread IS the rundown of what we know and don't know at this time.

Essentially there were problems with the kitchen we got for 3.3. We were challenged to get 3.5 working, and we are trying to get it working, rather than put too much effort fixing the 3.3 kitchen we got.

As for the "feature" differences, we havent really spent any time on that, and prolly wont until we get a stable install. The more people "try it" and tell us what works doesnt work, the more we can do to figure out and get it working.

For differences between 3.3 and 3.5 i'd sugguest you google windows mobile and see if anywhere else there are discusssions about it.

For me, I'm hoping for simply a better build, and A2DP working more reliably. Obviously there is not much of a fix out there for the A2DP in the other builds, so i put my engineers hat on and started testing away in "hopes" i'll get what i'm looking for. Its actually kinda fun if ya relax and be ready to flash multiple times.

[sfaure03]

shettj:

Couldnt build you're OEM w/o fixing up the rgu file. needed to add an extra '\' on lines 19 and 20 to escape the back slash.

Havent loaded on the phone, but that got the compile done.

Note that it gave a "dup file" for PhoneSetting.htm as well.

I just ignored that, and am gonna flash momentarily.

[Alwaysbelieve1]

thanx

[helmi_c]

Originally Posted by ImCoKeMaN

WARNING: Do NOT use this ROM if you are not comfortable flashing your device. It is in no way guaranteed to be a stable rom at this point, however aside from the noted issues it has been working well for me for the past few days.

Please read the entire post before determining if this ROM is right for you

Ok now for the fun stuff...

Here is AKU 3.5 it is in beta testing mode at the moment. I haven't had enough time to fix the USB support though (It does connect in bootloader mode). Activesync and file access via USB do not work (probly not teathering either, but i didn't try) Wireless sync works though so to sync contacts i suggest using mail2web before flashing then you can use that later to get them back.

Enjoy!

ftp://up.ppcgeeks.com/Apache/ImCoKeM...3.5_No_USB.zip

userpcgeeks
ps:ezupload

Once again USE CAUTION it's BRAND NEW.
Standard rules apply:
Be in bootloader first (dark screen says USB)
hard reset after (white screen press Y to clear mem space to boot)



Issues:
No USB support: I know about this one and this is my sole focus right now. USB does not connect with the PC (except in bootloader). This means activesync does not work for your contacts. In the meantime you can sync to mail2web before upgrading and then you will be able to get your contacts after you flash AKU 3.5 since wireless sync does work. For file transfer i use a usb adapter for the mini sdcard as a workaround now also.

Timesync: Yes i've gone through this too. I'm not working on EXT_ROM type stuff yet, but this can be fixed under settings ->phone -> services -> Time Synchronization. Just make sure to check the checkbox and hit update now. Watch the clock it should be accurate, but you can hit it again if it didn't take.

Are u using my kitchen (aku3.3/aku3.5) or really do the porting urself?

There must be Core base conflict with the ROM and the aku, if the core not fixed then U'll can never make USB work...

[ImCoKeMaN]

I used your kitchens 3.3 and 3.5 and did a bit of troubleshooting with the OEMs. The one that i think is causing the problem at this point is the ms2_usbfn.dll package. It seems whenever the following key is entered it locks lots of stuff up randomly and it is unstable:[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Usbfn]
"MemBase"=dword:40600000

I have tried using different drivers and changed MemBase to IoBase (and MemLen to IoLen) as that seems to be how all other 3.5 entries are. Also tried different addresses. I am able to get it to be stable with different IoBases or drivers, but nothing seems to get the USB to be recognized. The lights and charging work like normal though (with most combinations )

Sorry for holding out earlier. I was sparing the details thinking i was almost there, but since i didn't get it last night i wasn't as close as i thought. I know we have lots of other great minds out here (very glad helmi_c is on the case!) so hopefully this will help us get a solution more quickly!

[schettj]

Originally Posted by sfaure03

shettj:

Couldnt build you're OEM w/o fixing up the rgu file. needed to add an extra '\' on lines 19 and 20 to escape the back slash.

Havent loaded on the phone, but that got the compile done.

Note that it gave a "dup file" for PhoneSetting.htm as well.

I just ignored that, and am gonna flash momentarily.

Damn... posted the wrong one. The "right one" contains those changes...

[schettj]

Well googling around, that does seem to be a problem child

http://forum.brighthand.com/showthread.php?t=224198
http://groups.google.com/group/micro...50de1b3c5c75ac
http://groups.google.com/group/micro...dcd7747406591e

based on a lot of googling, looks like usbfn is all about activesync.

It seems you don't want to change the MemBase setting - is it possible that the default is set not to serial mode, but RNDIS and RNDIS is missing or otherwise borked?

If you put USB back in, but change the setting to USB Serial Mode for ActiveSync, does it become stable? Or, if it is already set that way, does changing it to the other setting make it stable?


MSDN info on USB FC driver

http://msdn2.microsoft.com/en-us/library/ms895495.aspx
and
http://msdn2.microsoft.com/en-us/library/ms923750.aspx

Best of luck!