Loading custom rom in emulater..

[MrBigKid]

Ok

I've decided to take the plunge and create my own Rom. However I want to customize it extensively.

I have the 6.1 emulator and was wondering if there is any information on inserting a custom ROM into the emulator for testing purposes. This would make it much simpler to test and change things for me without using the phone for it initially.

Any information or links to such would be greatly appreciated.

MBK

[PocketPcUser]

Originally Posted by MrBigKid

Ok

I've decided to take the plunge and create my own Rom. However I want to customize it extensively.

I have the 6.1 emulator and was wondering if there is any information on inserting a custom ROM into the emulator for testing purposes. This would make it much simpler to test and change things for me without using the phone for it initially.

Any information or links to such would be greatly appreciated.

MBK

Personally, this would be in-efficient to test for bugs and such. Most of the drivers that will be included in a ROM, probably won't even get activated and used, because the Emulator Set has it's own, if I am not mistaken.
Also, you wouldn't be able to verify if the device booted half way, or to the Today Screen, because it is software-based and not hardware based. Just to test general applications, the emulator is sufficient. However, this is why software companies still have to fix bugs, even after months of beta testing; a hardware device just isn't the same as a software-driven emulator. Mostly all software companies, or at least Spb that I can speak of, use both Emulator and Device testing, to ensure compatibility, but still end up at release, with a few bugs to fix. This is the reason that "flashing a rom to a emulator" would fail to provide anything worth much.
Anyone who knows better, feel free to correct me. However, based on my experience, software is not hardware, and a lot of bugs are hardware related.

[MrBigKid]

Ok that makes sense. Guess I was looking at it from the wrong perspective.
Oh well, it will be a pain but no choice for it.

I wonder if it would be possible to install the TF3D software in the emulator. Then i could port the visual changes over to the ROM builder. (still haven't figured out which kitchen I should use)

Thanks for the quick and honest response.

MBK

[ruskiyab]

It's actually very easy to import visual chenges with the dogguy kitchen. All you need to do is grab the modified manila files and throw them into the manila package folder

[MrBigKid]

I'm aware you can make the changes in the kitchen, what I am/was trying to do is have a simpler and quicker way for me to test my designs rather than having to flash my phone every time. I rely on my phone heavily and am also on call a lot so really did not want the downtime if I could get around it.

Speaking of kitchens which is dogguys? I'm aware of the Rice and the PPC kitchens. (although I haven't yet figured out what the difference between them is.)
MBK

[gguruusa]

Dogguy's stuff is a "kitchen maker tool". It make a stab at kitchenizing ROMs for Bepe's BuildOS. Sometimes it works better than others, but usually suitable for dabling in the kitchen making process.

eRice made a kitchen specifically for touch Pro based on Bepe's tools.
PPCkitchen makes a kitchen that works for many devices, one of which is the touch Pro.

eRice's kitchen will generally be newer (as long as he stays interested) than PPCkitchen. PPCkitchen is more tested and friendly.

PocketPCuser's analysis is correct. The WM emulator is designed to emulate a base WM device (kinda like a smartphone), without any additional hardware elements. The emulator is designed to test WM apps with no hardware dependencies - it is a far cry from device testing. As a general statement, rom customization is highly sensitive to the device so the emulator is near useless for that goal. You might try making your customizations as a cab before you try and oem them.

[PocketPcUser]

Originally Posted by gguruusa

Dogguy's stuff is a "kitchen maker tool". It make a stab at kitchenizing ROMs for Bepe's BuildOS. Sometimes it works better than others, but usually suitable for dabling in the kitchen making process.

eRice made a kitchen specifically for touch Pro based on Bepe's tools.
PPCkitchen makes a kitchen that works for many devices, one of which is the touch Pro.

eRice's kitchen will generally be newer (as long as he stays interested) than PPCkitchen. PPCkitchen is more tested and friendly.

PocketPCuser's analysis is correct. The WM emulator is designed to emulate a base WM device (kinda like a smartphone), without any additional hardware elements. The emulator is designed to test WM apps with no hardware dependencies - it is a far cry from device testing. As a general statement, rom customization is highly sensitive to the device so the emulator is near useless for that goal. You might try making your customizations as a cab before you try and oem them.

It feels good to be right once and a while,
Thanks for confirming my understanding.

[electronicrice]

Originally Posted by gguruusa

eRice's kitchen will generally be newer (as long as he stays interested) than PPCkitchen. PPCkitchen is more tested and friendly.

haha i like that. i've been pretty busy lately but i am hopefully going to be delving into a new kitchen shortly