PPCGeeks - 8 APR 09 - UPD 25: Mods please lock this thread!

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- CDMA TP Development (http://forum.ppcgeeks.com/forumdisplay.php?f=68)

- - 8 APR 09 - UPD 25: Mods please lock this thread! (http://forum.ppcgeeks.com/showthread.php?t=56777)

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

by the way, it is off of scott's website and the preferred ROM everybody likes. i have some small cosmetic issues with the one i have right now with the phone dialpad.

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Quote:

Originally Posted by zim2323 (Post 752597)

I have been working in the corporate IT field for almost 10 years. Most of which I have spent doing WAN/LAN Windows Server domain migrations, as well as Exchange 2000/2003/2007 Server migrations. The time that I have worked with Exchange I have become pretty familiar with the Windows Moble 6 SDK's. I have used them as a virutal "lab" to test, configure, and troubleshoot mobile user issues with phones, etc.

http://www.microsoft.com/downloads/d...displaylang=en

Is there ANY way that these tools can be used as a testing ground for new ROM's before they are deployed to phones. The best example that pops into my head, is being able to test UC or Sushami(?) scripts at first boot before you push them to the phone. Once you have everything working good there, you could do live tests on your actual phone.

I've been reading the UC documentation I was pointed to and I'm looking for someplace to test what I'm doing without having to reflash the phone everytime I do it. I'd rather just build the UC script one step at a time.

I'm uncertain what you are trying to test... I've also served in the IT realm for 4 years a while back.

UC script is dead simple, as it only has a number of commands that it can execute. XMLs are required for provisioning registry settings.

Sashimi is even simpler as it only requires you to store Cabs, and Regs into a specific folder in your SD card for auto or manual execution.

In terms of Mail Account setups, Exchange/IMAP4/POP3, they are all provisioned from a single or multiple XMLs.

Of course regular rule for a Valid XML schema must be followed including omitting the usage of special characters and replacing them with XML equivalent. Such as & = &

Sashimi allows you to run anytime you'd like, while UC is ran after the Initial boot of a ROM Flash. The downside to UC especially when using ROMs that has Autocalibrate scripts... You will not be able to use your touch screen to click OK on messages that pop up. You can HIDE the UC window and UNLOCK the screen, but you'll need to use the Dpad to interact with any popup windows.

Let me know if this answers your question.

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Quote:

Originally Posted by RONMAC (Post 752604)

S2U2 = FREE :headbang:

Pocket Shield = $12.90

LoL nice comparison...

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Quote:

Originally Posted by clubprerit (Post 752608)

i cannot get this to open right:
[CE OS 21015 Build 21015] - Rev C2 - Stable!
the zip file opens with two folders:
sys & rom, but the .nbh file is nowhere to be found. anybody know how i can get this installed?

Is this a CE OS from the kitchen? If so, did you download the Kitchen C2beta? Look at the #2 post of this thread. It explains everything there.

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Quote:

Originally Posted by clubprerit (Post 752608)

Your .nbh will be created once you cook your rom that build is for the kitchen. Drop those two folders into the the kitchen folder and cook up something fun.

Rob

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Im running rev C2 with CE OS 21015 and having issue with Battery Indicator on the top right. It will display Battery when it is plugged in, display plugged in when on battery, it will show the battery at 20% even if it is fully charged. It is very inconsistent. When I plug in the phone the indicator will not switch to show external power immediately. Eventualyy it will display the correct data but it takes a long time to update to the current battery status.

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Quote:

Originally Posted by rab669 (Post 752724)

I'm running exactly what you are, with only the selectable options differing. I have not had the same issue, so I have to ask the obvious, when you cooked your rom, did you make sure that BOTH battery icon options were not selected? Irregardless I would recommend recooking the rom and flashing the phone. 21015 has been pretty stable for most users.

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Quote:

Originally Posted by rab669 (Post 752724)

Are you a Sprint user?

Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Quote:

Originally Posted by jucytec (Post 752614)

You gave an "answer" and asked a question that had nothing to do with my question.

What I'm trying to accomplish is just what I said the first time. I want to create a VIRTUAL environment to test in rather than reflashing the phone to test for each change. I've actually got the 6.1.4 SDK installed and testing SEVEN application with it right now. I can "hot dock" the virtual device and play DIRECTLY with it without screwing up my phone in the mean time.

Neither UC or Sashimi really have anything to do with the question other than this would make testing them easier.

The question wasn't why should I not use virtualization.

The question was and still is, has anybody tried to utilize the Windows Mobile SDK virtualization tools as a testing platform for testing new ROM's?

If was and dropped, what were the reasons? Maybe there are too many limitations on this. The mobile virtualization product that VMWare demo'd at Mobile World Conference really sparked this interest.

Thanks!