Custom OEM Requests ...Get them here! Updated: 4/18/09

[rstoyguy]

Originally Posted by Vancer

When I make an OEM with OEM Package Creator I notice that many of the files have 000- in front of them. and this is represented in the initflashes.txt as well. Then when I look at the OEMs from the PPCGeeks_OEM.rar, none of these OEMs have the 000- in them. Do you know if they just went in and removed the 000- from the file names and the associated syntax in the initflashes files? Or maybe they were created a different way or created with a different version of OEM Package Creator?

When I first noticed this difference b/t the PPCGeeks OEMs and the ones I created it made me hesitant to use mine and think I was doing something wrong.

The 000- is to prevent duplicate files when creating a rom, this can be turned off when you first open the package creator.

The ppckitchen oem's, their approach is to leave the files in \windows if possible to save phone memory space. (When you cook a rom, ALL files get permanently placed into \windows) But on my vogue which has plenty of memory, I try to have my oems put them on the device as the author intended. This way making skinning/upgrading to a newer version easier. While either way is ok, I prefer my way...

Originally Posted by xd1936

Hmm... That OEM kinda worked. The .mscr files had the right icon, but I got the 'not a trusted certificate' error... I'll try again later, unless someone else has an already-built one

You need to ask in the PPCKitchen thread how to relax security in your rom... I don't use the ppckitchen, but it does work fine in Dogguy's kitchens.

[rstoyguy]

Originally Posted by xd1936

Is there an OEM that I'm missing that does Mortscript 4.1?

http://www.sto-helit.de/index.php?mo...n=view&menu=29

The CAB doesn't have a _setup.xml, so I'll try to put one together by hand

Originally Posted by xd1936

Alright, I have a TEST VERSION (READ: BETA) of what I came up with...
Mortscript 4.1

Download and put the folder that's zipped up in the USER_OEM of the Kitchen

I'll be testing as well... Lemme know if there's any problems. I'm kinda iffy about the Registry changes I had to make, so feedback please!

-Link Removed; files not assosiating correctly-

I think I missed something, but there is an OEM version of mortscript here.

[Whosdaman]

Originally Posted by rstoyguy

To apply the hotfix to the v1.13 OEM do the following:

1. Extract the archive.
2. rename ilock.exe to 000-ilock.exe
3. copy to your OEM directory

Done.

I will not be updating the S2U2 OEM until a more stable/final version is released.

I do this as a hobby, I can't spend 2 hours doing an oem just to do it again the next day....sorry...

TYVM!!!

[rstoyguy]

By popular demand...

OEM_S2U2-1_14-QVGA.................................Slide 2 Unlock v1.14


OEM_S2U2_S2V_S2P_Megapack_v1.14............Mega S2 Pack v1.14
Includes the following 3 Apps from A_C:
--- Slide 2 View v0.38
--- Slide 2 Unlock 2 v1.14
--- Slide 2 Play v0.40
-- Updated S2U2 to v1.14 8/4/08
-- And restored original graphics in S2U2

I got bored....

[puff]

Originally Posted by rstoyguy

I do this as a hobby, I can't spend 2 hours doing an oem just to do it again the next day....sorry...

Originally Posted by rstoyguy

I got bored....

Ok first i gotta say thanks for all your work, you've easily poured hours into this thead...
Now having said that, you gotta appreciate the irony in these 2 posts

[rstoyguy]

Originally Posted by puff

Ok first i gotta say thanks for all your work, you've easily poured hours into this thead...
Now having said that, you gotta appreciate the irony in these 2 posts

Well this update was a 1 file deal. Unzip, copy to folder, upload...This took all of 10 minutes tops...

[DHarvey]

Originally Posted by rstoyguy

By popular demand...

OEM_S2U2-1_14-QVGA.................................Slide 2 Unlock v1.14


OEM_S2U2_S2V_S2P_Megapack_v1.14............Mega S2 Pack v1.14
Includes the following 3 Apps from A_C:
--- Slide 2 View v0.38
--- Slide 2 Unlock 2 v1.14
--- Slide 2 Play v0.40
-- Updated S2U2 to v1.14 8/4/08
-- And restored original graphics in S2U2

I got bored....

The built in volume controls, the main reason for upgrading to 1.14 do not work with the OEM.

[rstoyguy]

Originally Posted by DHarvey

The built in volume controls, the main reason for upgrading to 1.14 do not work with the OEM.

Does it work from the .cab install? I'm getting the same...May want to bring it to A_C's attention..

Originally Posted by A_C

Hey guys,

Although S2U2 is now called v1.13, it doesn't mean it can be run perfectly on your device. Thanks to different devices produced by different vendors. So, please test it before use it everyday, especially the CallerID function.

[nipplar]

rstoyguy,

I would love some oem action with prssreader, mlasqfm and pocket tea. All are now open source by andrsd (maker of batti) and are some of my favorite apps.

also no big, but the opera 9.51 beta oem doesn't work for me. it seems that when you launch the shortcut (operaL.exe) which references opera9.exe it doesn't go past the load screen. I think it might be because they are named 000-opera9.exe and 000-operaL.exe in the windows folder, but not sure.

Thank you for your work! =D>

[DHarvey]

Originally Posted by rstoyguy

Does it work from the .cab install? I'm getting the same...May want to bring it to A_C's attention..

Well the volume controls work great in the Cab installer. I also noticed that your initflashfiles.txt neglected to include the png images for the volume control.

Directory("\Program Files\S2U2\gfx"):-File("vcbar.png","\windows\000-vcbar.png")
Directory("\Program Files\S2U2\gfx"):-File("vcbg.png","\windows\000-vcbg.png")
Directory("\Program Files\S2U2\gfx"):-File("vcbutton.png","\windows\000-vcbutton.png")
Directory("\Program Files\S2U2\gfx"):-File("volume.png","\windows\000-volume.png")
Directory("\Program Files\S2U2\gfx"):-File("vtopbar.png","\windows\000-vtopbar.png")

That was all left out and I added it to the initflashfiles.txt but still no worky.

The files were there but the initflashfiles.txt was missing it. Now what I'm guessing is that when you install the cab and s2u2 is running in the backgound, the volume controls are taken over by the program but by disassembling the cab file it corrupted it somehow.

I thought about just having it install during customization to get the volume controls working right but that would kind of defeat the purpose as I would not be able to use custom graphics..