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

Kamokazi · #**1131** (**permalink**) 03-04-2009, 02:21 PM

Quote:

Originally Posted by zim2323

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!

Lots of reasons. Hardware drivers, radios, carrier-specific stuff, long-term stability, etc. Emulators are not good for testing ROMs. They are good for developing and testing applications, however. You may be able to test sashami, etc just fine with it.

Also the mobile virtualization thing is kind of silly...the use is very limited. The most practical thing I can see is having a dumphone OS for most purposes, then switching to a full-featured OS for web-browsing and other apps.

Really, what I think is that VMWare is struggling to find alternative business models, because the products that are currently being used with their virtualization software are starting to build in features with the same benefits of virtualization in for free (or they're just flat-out including virtualization ala Hyper-V, XenServer).

But really this is starting to get out of the scope of the thread. I am interested in trying it to see how it works now myself. UC Autorun and Sashami may work with an emulator...I haven't messed with the emulator enough to know for certain.

rab669 · #**1132** (**permalink**) 03-04-2009, 03:00 PM

Quote:

Originally Posted by impudent1

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.

I am not sure if i selected both. I will recook and retry.

thanks

Nimdock · #**1133** (**permalink**) 03-04-2009, 04:54 PM

Quote:

Originally Posted by rab669

I am not sure if i selected both. I will recook and retry.

thanks

I will ask you again. You may think it is irrelevant but it is not.

Is your carrier Sprint?

I ask you because I use Sprint and I have had similar issues when cooking with this kitchen from time to time. If it's not Sprint then just never mind.

DigitalAttic · #**1134** (**permalink**) 03-04-2009, 05:07 PM

Quote:

Originally Posted by zim2323

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!

From the looks of it, the effort to do what you seek w/the MS Developer Tools is far too complex and time consuming for the average user. If you were interested in developing an application for commercial use, I would say go for it. On the other hand, if you are just a hard-core developer and want something to play with, go for it too. But my take on this is that it is not at all intended to be a test-bed platform in the way that flashing and UC/Sashimi provide. This is a tool for testing WM applications in a development environment.

Now VMware's MV is a very interesting piece of software, a mobile phone hypervisor. But the description they give isn't clear on whether a WM VM can be made using it, though it is alluded to; and that is basically-- IMHO-- what you are looking for, and that would be great to test with.

I have been using a set of tools to abstract the application and settings space from the WM OS so I can redeploy effortlessly to new WM ROMs: PM me if you are interested.

One last thing on WM Virtual.: I noticed Android was absent from the list of supported OS'es... hmmm.

TC - DA

Nimdock · #**1135** (**permalink**) 03-04-2009, 09:21 PM

Ok, since Scott is MIA I'm thinking maybe I should just jump and start breaking my phone, hehe.

impudent1 · #**1136** (**permalink**) 03-04-2009, 09:39 PM

I think Scott's wife hired somebody with his ROM money (which goes to her paypal) and had his mouse hand broken.

Nimdock · #**1137** (**permalink**) 03-04-2009, 09:55 PM

Hehehe, I like that theory... But that that would mean I helped.

oldman · #**1138** (**permalink**) 03-04-2009, 10:10 PM

IMpudent: Check you PM

Bob

Billy_Bob · #**1139** (**permalink**) 03-04-2009, 11:05 PM

For the first time since loading my phone with SSK1.5 20764, I used my phone all day for various tasks and I must say what all of you already know - these ROMS are a vast improvement over the stock phone.

It finally functions as it should and is much more smooth than the stock phone. Previously there were all these pauses and stops when I switch tasks and hit buttons, now it is really smooth.

I know people will tell me how much better and faster the new ROMS are. But I just wanted to remind eveyone how bad the original was - you've probably forgotten because you've been using Scotts ROMS for so long.

Even the old ones ROCK!

I've got a date in the kitchen to cook up something new with 21015.

Thanks again guys - especially Scott!

jucytec · #**1140** (**permalink**) 03-04-2009, 11:32 PM

Quote:

Originally Posted by zim2323

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!

I see what you are saying now! LoL I wasn't even close...

But as you already know running an instance of any OS via Virtual PC or VMWare will always have it's limitations. if you were to test you'll simply be emulating the OS through a window, and in Windows Mobile SDK's case, you'll be simply testing just the software side of things... Most of the harware components will be emulated, which may not actually test any hardware components on your windows mobile device.

My company does windows mobile development, and while we do recompile some of the applications to run on x86 Windows platform; we only test the recompiled app to spot out basic usability issues/GUI design issues. Qualifying the actual software has always happened on the device inately.

of course this is only my opinion and means nothing...