Fully working Helmi AKU 3.5 kitchen PPCGeeks revision

[colonel]

Has anyone checked to see what the page pool is set too? This could be a cause of this.

[schettj]

My 3.5 program memory is holding steady - been running for about 18 hours since last reset, it's 25 used/22.19 free (after reset about 18/29) seems to ramp up to mid 20s and then hold steady there (once glyphcache & buffers are allocated)

[finster869]

IMCOKEMAN-- I see you have a r3 up on the ftp server now for the 3.5 helmi kitchen. Can you post the changes since the 1.1 kitchen?

[evans]

Okay, I managed to figure out the Verizon info for MMS - I installed the CAB in the ExtRom, found the settings there (verizon version is 3.0.6 newer one I have is 3.0.16 - prolly no real difference).

In any case, I then uninstalled the Verizon one, which restored the version from the custom ROM I built *and* kept the connection settings in the registry.

In case anyone wants to enter them manually:

Server Name: Verizon Wireless
Gateway:
Port Number: 80
Server address: http://mms.vtext.com/servlets/mms
Connect via: The Internet
WAP Version: WAP 2.0

[ImCoKeMaN]

Originally Posted by finster869

IMCOKEMAN-- I see you have a r3 up on the ftp server now for the 3.5 helmi kitchen. Can you post the changes since the 1.1 kitchen?

It's the same kitchen as the R2, but i added the USB patch. You can check the first post in the original (no usb) 3.5 thread for details, i updated it a bit. I didn't try to publicize it though with all the other customs as i don't plan on updating that kitchen very frequently at this point and now we have a good baseline to start from. Well it may have a few quirks, but it's been pretty good for my use at least.

[boe]

Issues -

1. Live Search - loads, but I can't link to contacts from within Live Search - will fail - ELKAY - LIVE SEARCH LOADS - but live search will not link to contacts. Using the latest version of live search from http://mobile.search.live.com/client/download.aspx - tried it with .net 1 in helmi 3.5, tried it with 2.0 and 2.1 - no luck - no other software loaded. Also using the center joystick to zoom in doesn't seem to work reliably - did with 3.3. Again contacts and calendar work normally - only trying to use the choose contact from WITHIN live search will it crash live search.

2. Lost ongoing call when received incoming call. Only happened once so far.

3. Can't use ## to do PRL update.



Things that are great about 3.5

1. So far not a single DSOD - would have happened repeatedly by now even with AKU 3.3

2. Fast bootup - much better than Sprint 2.x

3. Great selection of icons!

4. Not sure why but BT headset seems better than even AKU 3.3

5. Battery life seems better for me than aku 3.3 BUT some have said otherwise.

[dc]

Originally Posted by boe

1. Live Search - loads, but I can't link to contacts from within Live Search - will fail - ELKAY - LIVE SEARCH LOADS - but live search will not link to contacts. Using the latest version of live search from http://mobile.search.live.com/client/download.aspx - tried it with .net 1 in helmi 3.5, tried it with 2.0 and 2.1 - no luck - no other software loaded. Also using the center joystick to zoom in doesn't seem to work reliably - did with 3.3. Again contacts and calendar work normally - only trying to use the choose contact from WITHIN live search will it crash live search.

I too am running this 3.5 ROM and have the same problem with contacts not working in Live Search. Incidentally, the contact function used to work on my Helmi 3.3 ROM. I noticed that an error log entry was created called LiveSearchError.txt as follows:

2/18/2007 1:14:13 PM
Version: 1.0.2592.31374
System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.
Flow.Forward: System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.DirectionsView.Cho oseLocation: System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.DirectionsView.Cho oseEndLocation: System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.Flow.Forward: System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.

While the above doesn't mean much to me, I thought it might help others in finding a solution.

[lightsail]

For the ##PRL# thing, I wrote and utility for it. It is here.
http://www.ppcgeeks.com/new-code-dia...3-5-t2919.html

For the LiveSearch Contact issue, I checked the .NET CF2, it does not have that Microsoft.WindowsMobile.PocketOutlook.dll. I tried copy the dll from the SDK to the local folder or windows folder, it did not help.

[ImCoKeMaN]

Thanks for writing that app lightsail (even though i haven't tried it yet ) ! I have added a link to your thread in the first post.

As for this live search deal this should head us in the right direction. I wonder what Celedial uses to make this contacts lookup work. I guess it would be best to be able to work out the old method though since that could make the old smartdialer work as well as the live search contacts at the same time.

[colonel]

Originally Posted by dc

I too am running this 3.5 ROM and have the same problem with contacts not working in Live Search. Incidentally, the contact function used to work on my Helmi 3.3 ROM. I noticed that an error log entry was created called LiveSearchError.txt as follows:

2/18/2007 1:14:13 PM
Version: 1.0.2592.31374
System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.
Flow.Forward: System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.DirectionsView.Cho oseLocation: System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.DirectionsView.Cho oseEndLocation: System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.Flow.Forward: System.TypeLoadException:Could not load type Microsoft.WindowsMobile.PocketOutlook.Contact from assembly Microsoft.WindowsMobile.PocketOutlook, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.

While the above doesn't mean much to me, I thought it might help others in finding a solution.

Okay, this is a start. This is the same type of error that occurs when I try to run IDTransfer.

System.TypeLoadException:Could not load type Microsoft.WindowsMobile.Status.System from assembly Microsoft.WindowsMobile.Status, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35.

While this is slightly different, this may be the key to both issues.