ROM Kitchen 1.0.0.10 Release Candidate 1 (Updated 3/8/2007)
 

Please do not distribute this ROM and/or ROM kitchen, as it has not yet been completed. Please wait until a final version has been released before allowing others to obtain it.

Potential issues remaining:

• .NET CF versus .NET CF 2: According to this page, .NET CF 2 is now the default version shipped as of AKU 3.0. So it's probably not a problem that we ship .NET CF2 in addition to .NET CF in our ROM.
• According to that page, Modem Link has, in fact, been deprecated. So we can probably remove it completely.
• 3/8/2007: Numerous people have indicated problems attempting to run Wireless Modem. One involves the "COM OPEN ERROR" problem (issues duplicating the error?). The other involves not being able to run Wireless Modem under certain circumstances, and needing a soft reset to re-enable it (referenced by JBabey here, and I've hit the problem myself as well, although I need to find out how to reproduce).
• 3/8/2007: Bluetooth PAN is still an issue. There appear to be conflicting reports on whether or not PAN works or not (performing a quick Internet search). Menneisyys wrote up an article expalining the change in the dial-up networking model changes in AKU 3.x. For Windows Vista, there's an article explaining how to connect to a Bluetooth PAN. It would be nice if we could find a device where Bluetooth PAN does work, and determine whether or not the DLLs there are usable or not. According to Menneisyys' article, certauin Himalaya, Universal, and Wizard ROMs have Bluetooth PAN support.
• 3/8/2007: A shortcut to the Camera is missing. Other shortcuts may be missing as well, so somebody should load the official AKU 2.x ROM to ascertain which ones are actually missing.
• 3/8/2007: As mentioned in this post, we should update to .NET CF 2 SP2
• 3/8/2007: As mentioned in this post, OggSync and GMobileSync has issues with either Pocket Outlook and/or .NET?

Please post any other potential issues in this thread. Thank you.

Updated: March 8, 2007

The problems with the ROM have been fixed. Programs can now be installed properly, and the Favorites button in Pocket Internet Explorer performs as expected. The ROM version is available on the public FTP site here:

ftp://up.ppcgeeks.com/Apache/Project...0.10%20RC1.rar

The password for the .rar file is attached to this post in a .zip file. And in case you're wondering, yes, I have actually verified that this works myself. :wink:

Notes: March 5, 2007

The kitchen version of the ROM kitchen 1.0.0.8 RC1 is available on the dev FTP site, under the ROM Kitchens directory, as "WM5 AKU3.5 ROM Kitchen 1.0.0.8 RC1.zip". The ROM version is available on the public FTP site here:

ftp://up.ppcgeeks.com/Apache/Sogarth....0.8%20RC1.zip

Please PM me the dev ftp site address.

Thanx

It's a file attachment in the documentation forum, in the FTP info thread. If you don't have access to it, you'll need to take it up with Wideawake....

nice job, thanks! So if the .net2.0 thing is sufficent, then I'm off the hook for further work on it? If so I can just focus on documenting this - I may be able to get some time in today and burn the sucker ;)

Should I start a separate thread with instructions for the QA testers to report problems in or do you want them to use this thread. Doesnt matter to me either way.

OK, I must be doing something wrong. When I hit start in createos.exe it tells me:
Error: OS\.ROM missing.


Am I missing something?

Are you wanting testers to only use the base ROM version and not the kitchen? I'm flashing the base ROM right now.

One thing I noticed on the PR2 ROM i was running until I just erased it was that in notifications when I set email to not display a message on the screen it still shows a message weather I check the box or not. This will be one of the first things I test once I flash this =).

Does this ROM have fixes for live search contacts lookup? Or is this a known bug of this release?

Firsrt Issue I've had with this ROM:

when trying to install my private certficate for push mail from my storage card, I recieve an error "cannot access certficate."

I also tried to install pocket e-sword and got an error that "installation was unsucessfull".

So I'm thinking that it is a problam reading my SD card. more info to come ....

update:

hmm nope it isn't a problem with my SD Card. Even when I copy things to the device using active sync they still won't install. It seems i can't install anything with this ROM? *shrug*

I will post the thread on how to report a defect tonight, as I have the documentation at home.

RIIIGGGHHHHTTT.... I just slapped it on my spare fone... slapped it on, hard reset, and reset it when it says 3 seconds to load the vzw customizations... IE favorites takes you to the windows directory. History takes you to the windows directory. Connections tab is hosed, it flashes up for a second and then its totally blank. If I go to advanced, I can choose select networks and add a new one from there, but the tasks screen is blank. If I do add a new one, then the tasks tab functions properly.

Also, once I have made the connection, and I re-open IE, I entered www.google.com on the url bar, and it did not automatically dial the data connection, rather just gave me an error about it not being able to reach google. I manually dialed the connection, and made sure to close IE / restart a new one, and still no internet.

(also tried all of these after another hard reset/don't let it run any of the customizations, and also a "clear storage and not let it run any customizations. Same issues as above.

Well, back to the drawing board.

**EDIT** I was using the rom posted above, not the kitchen to roll my own. I don't have that much freetime right now.

**EDIT2** Using vxUtil, I was successful at pinging www.google.com, so we know that the connection is good, and dns is functional. Must just be IE... possibly something to do with removal of the old homepage stuff?

Yeah I flashed back to 1.2 PRE2 for the moment untill there is a reason for me to do more testing on this =).

.ROM folder and .VM folder
 

It appears as though the .ROM folder and the .VM folders are missing from the OS folder in the kitchen for this release. That is probably why people are getting an error trying to cook with it.

Anyone trying to cook, please copy the .ROM and .VM folders from OS in the 3.5r2 into the OS folder for this release and see what happens.

Ok, after adding the .ROM and .VM folders to OS, I am now able to start the createos.exe. However, I am getting the following error when trying to cook:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.UnauthorizedAccessException: Access to the path 'C:\Downloads\windows mobile 5.0\Custom Rom builder\WM5 AKU3.5 ROM Kitchen 1.0.0.8 RC1\Fin Modified WM5 AKU3.5\Temp\boot.rgu' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter.CreateFile(String path, Boolean append)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding)
at CreateOS.Form1.button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
CreateOS
Assembly Version: 1.0.2371.28156
Win32 Version:
CodeBase: file:///C:/Downloads/windows%20mobile%205.0/Custom%20Rom%20builder/WM5%20AKU3.5%20ROM%20Kitchen%201.0.0.8%20RC1/Fin%20Modified%20WM5%20AKU3.5/CreateOS.exe
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.163
Win32 Version: 8.00.50727.163
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727. 163_x-ww_681e29fb/msvcm80.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Any ideas????

I'll investigate the disappearance of the .ROM and .VM folders, which confuses me because they should be there. It's entirely possible that my zip program refused to see them. :roll:

The .NET errors are due to the majority of the files being read-only. I'll address that in all future releases so that it doesn't happen again (including the one I'll be upping shortly to deal with these current issues).

Does anybody know what TheRocoLoco is hitting up against? I suppose it could be a possibility that the files being read-only carries over to the device...?

I'll toss another ROM and another ROM kitchen up to see whether that works better. I'll update this when they're both up, because it would be good if we could actually get something working. :wink:

The ROM is now available in this location instead:

ftp://up.ppcgeeks.com/Apache/Project....0.8%20RC1.rar

I've changed it to be a .rar archive, and this time, the files should all be non-read-only (which will hopefully fix the really mysterious issues). Since it's password protected, the password is: unikitchenrc1

The kitchen is currently being uploaded to the dev FTP site. Similarly, it is now a .rar archive, all the files in it are non-read-only, and I've confirmed that the .ROM and .VM directories are in it. Uploading should complete in a little over 10 minutes.

Cool, Im glad it wasnt me. :)

I will try it today!

Downloading now and cooking later!

Well that was fun. I am running this now and have found out a few things.

1. Hitting "favorites" within PIE causes File Explorer to pop up...
2. Tried to install an application via cab file and discovered that ANY cab I choose fails... Tried Cert_SPCS, Cert_SPCS.sa and several others.... No workie...

Sorry, I didnt see the post above. I am seeing all of those issues as well as the inability to install cab files.

Grr... very disappointing. I'm guessing I might have to give up my mostly-stable 3.3 installation, back up all my data, and then start reflashing ROMs again to try and figure out what's going on (I was personally kinda hoping to be able to hold off until this stabilized before going through the ROM cooking process again). That is, unless somebody else can figure out what might be going wrong? :D

First post updated.

woohoo!

So far it looks great. Everything I have tried so far has worked... Except BT PAN but I didnt figure that was fixed yet....

:)

Ok so *this* is the stable one then :D

I'll try and cook a rom with it and start the documentation efforts, but real life is closing in hard, and it looks pissed.

:p

Additional notes regarding current issues. I'll see what I can investigate, possibly this evening. I may be another person who might be able to look at the Bluetooth PAN issues.

I have dloaded it, and will begin testing this weekend.

Bluetooth Pan
 

Can someone who wants to use Bluetooth Pan check if this alleged fix really works?

http://ppcgeeks.com/aku-3-5-bluetoot...xed-t3670.html

If so, then we are almost finished repairing evertyhing we wanted to fix for a perfect kitchen.

I just read that. Unfortunately, I don't think that can be called a fix in regards to out efforts here. The way I understand that "fix", you have to install a different BT stack on the PC and I assume the PPC as well. To me, this is no different that getting the third party app (can't remember the name) and using it for BT DUN. I will still check it out, but following the idea that the kitchen release should be a "stock MS" rom, I do not think this is the proper fix.

Ok, I didn't catch that. If it is using a different stack, then I agree with you 100% Colonel that it is not a true "fix" necessary to meet our goal.

Well, in rereading it, I guess you only need different BT stacks on the PC and it appears that it is being shipped as part of a rom. I do have to question that MS would ship a rom that needed a BT stack other than their own. Unless the change was made somewhere else down the line, it just seems a little fishy.

Bluetooth PAN Working for me on .10 RC1 /w AKU3.x_BluetoothPAN_Fix.CAB. This is what I did and it worked the first time.

1. installed the .cab
2. added the PPC to windows vista (via "Add a Bluetooth Device")
3. clicked connect in internet sharing /w bluetooth PAN selecteed
4. choose "Join a Personal Area Network" in Vista and tada it found it and worked.

Pocket PC and Laptop using the PPC connect at the same time .. sweet ..

additional details on my setup:
VX6700
Dell Latitude D620 running Vista Ultimte RC2 build 5744
using the internal bluetooth (Dell Wireless 350 bluetooth Module)

I'm not using any drivers except the ones that got automatically installed with Vista.

I'm not getting very good speeds though 230kbps down and 80kbps up when I just tested it .... I'm in an EVDO area, not sure what I would have gotten using BT DUN on a 2.2 ROM as I never used it. So maybe this is just my phones fault or something.


Also button 5 still gets broken when you install VC 1.6 but it is fixed the same as before http://www.ppcgeeks.com/voice-comman...tton++fix.html

I'm also thinking that bluetooth PAN is a large battery drain ..

After 1 day of testing, here's what I have so far.

Paul

---------------------------

TODAY SCREEN ITEMS
All fully functional

CALENDAR
Added calendar appt, reminder functional

TASKS
Added task, reminder functional

ALARM
Added alarm, functional

MSN
Fully functional

TITLE BAR & TRAY ICONS
Fully functional

START > PROGRAMS
LINKS: All present links fully functional
MISSING?: PocketMSN
PROGRAMS TESTED:
GAMES: Fully functional
ACTIVESYNC: Sync local PC as well as Exchange Server with Direct Push
Did not test "Connect via IR" or "BT"
Installed self-signed SBS2003 cert from storage card, listed in Root certs
Push works perfectly
CALC: ok
INTERNET SHARING: Fully functional, 133Kb/s according to bandwidthplace.com
WMODEM: ***NOT*** functional, Add New Hardware wiz could not install "Serial" device
VOICE DIALER: Fully functional with Plantronics 640 headset
ZIP: Created zip archive, added files, viewed files, deleted archive successfully

START > SETTINGS
PERSONAL: All fully functional
SYSTEM: All fully functional
CONNECTIONS:
BEAM: successfully sent and received beamed .pwi files
VPN: successfully connected to vpn, disconnect button present and functional after tapping EV icon
BT: successfully connected to Plantronics 640 headset
WIFI: successfully connected, disconnected, then connected to net using EVDO
WLAN: correctly displayed wifi stats while connected, tray icons functional
WIRELESS MGR: fully functional

INPUT TYPES
Block, kb, letter recog, phone pad, transcriber: All fully functional (tested in Notes)

ALL-AROUND BEHAVIOR
0 lock-ups, 0 DSOD. Powered off at night, not frozen in the morning.

TO-DO:
Leave charging in cradle overnight, see if frozen in morning.
Power off at night, initiate call first thing in the morning using BT headset voice dial (have noticed lock-ups on other roms.
Tell me if I missed something...

Nice rightup!

todo
Verify uncheck use advanced networking in activesync
verify smart dialer ok

The wmodem thing is odd - wmodem should work if you've installed activesync.

w00t!

BT PAN working!!!!! You are the man!

As we discussed, you need a specific inf file to connect using wmodem (on a Windows PC). I've attached it to this message (no need for the dialer app though).

Nice report!

OK. So will we put this BT fix in the kitchen?

Hmmm...it didn't "spring forward" to DST. It should have, right?

I noticed that as well. But what is really perplexing is that WeatherPanel shows the right time, but my device time does not...

I cheated and installed the DST cab file from microsoft even though I had heard it wasnt needed.....

My time changed just fine...

Under Phone options, time, I am set to sync the sprint network. Day light savings time updated without issue.

Just noticed it work, yet my appointments are off...oops!

I dont have time synchronization checked, and mine updated. Still using colonels rom though.