OEM question
 

Almost gotten to that elusive "perfect rom" point but would love to have everything in it if I ever have to do a hard reset. Are there any OEM's for phonealarm, wa2, the zphone dialer, and the finger flick contact manager that would work with the helmi 1.0.1 kitchen and are stable? I love the new kitchen and appreciate all the effort that went into it, and can't even imagine all the time you all must have spent getting it up and running. Thanks in advance.

Phonealarm and stable don't belong in the same sentence together. But yes there is an OEM and no it doesn't work properly. It is one of a handful of apps that will functionally come together as an OEM but doesn't work properly in that form.

Technically you could do it by copying all of its files to its usual install location in \Program Files but doing that makes it take up the same amount of space as if you had just installed the cab file.

I don't have any specific knowledge of the Zphone dialer but most 3rd party dialers break ## codes, smartdialer, and the ability for the data arrows in the top bar to turn grey to indicate a dormant data connection. As long as you accept those potential limitations then there's no reason you can't use it as an OEM.

Not sure about the others but Wisbar is another app I stay far away from due to it's resource-hogging ways.

As for WisbarAdv2 and WAD I posted a builder for it so you can make your own custom OEM with your own theme, etc. Read through that post for directions. (Link is in my signature)

I use the Phone Alarm 1.60.2 OEM. It's on the FTP somewhere, likely under old OEMs folder.

Ive used this OEM successfully. It isn't the most stable app Ive ever used but the advantages far outweigh the occasional stability issues. The OEM seems just as stable as the cab install imo.

~Despiser

Thanks for the responses. I don't seem to have much of a stability problem with Phone Alarm 1.60.2 as a cab install, so I may try the OEM and see if it works. As for wisbar, I am willing to take the performance hit (not really noticeable in most instances but boot-up) and really like the features it adds. As to the zphone dialer, I use it all the time. Doesn't break the ## codes, and the smartdial is there. Also it is very easy to mod the buttons and background to whatever your liking. Can't tell you on the arrows, as my wisbar theme doesnt support them. I'll try with what i've been given here, and go from there.

Oh, has anyone successfully made TomTom Nav to work as an OEM? Couldn't find anything on it, but I am going to give it a whirl as my first attempt at OEM creation. As long as I don't figure out a way to let all the smoke out of my phone, it should be a learning experience lol!

namopereht

TomTom always seemed pointless to me as an OEM because you need to have your SD card anyway for the maps. So the next time you install it from CAB, copy the whole Navigator directory over to your SD card and voila--never have to install it again!

I think someone did make an OEM for it though, sorry I'm not sure who or when (or what version) but I think I remember seeing someone mention it.

Using that method you could just add a shortcut for TomTom into one of your other OEMs too. Then there's really nothing to do.

Yup that's exactly what I do, for TomTom as well as several apps which are either too big or cannot work as OEMs. If the app has reg entries you can also put those into a custom OEM in the kitchen. It's really slick and so gratifying to hard reset and have everything already set up :)

Re: OEM question
 

Ya I was making the contact manager OEM, then ran into a brick wall cause my laptop not running BuildDSM.. I check my OEM xml and initflashfile but I dunno why I cant finish my oem's dsm file...
Anyone care too look & finish here it is:
EDIT: I finished it in another laptop.
Now have 2 see why BuildDSM is picky and doesnt want to run on my main laptop.

It just built into my ROM fine how it is...