Problem: Re-cooking personal ROM (saving sounds and volume control)

[mccune]

I've been reading an gathering information for weeks now to build my own personal ROM. Since I'm unable (at the moment) to build one from scratch ;)

Somehow it doesn't seem to work for me and I could not find an answer to my problems. I really hope some ROM Guru is willingly to help me out here.

I've used the Diamond Kitchen (http://forum.xda-developers.com/showthread.php?t=405371) to extract the NBH files. And like it should it creates the OEM and SYS folders when you don't use protected ROM's like Dutty's, Swtos or Bepe's.

I've tried multiple ROM's to rebuild for my personal needs. And here are the most common problems I've encountered:

- Diamond (or Raphael) Volume Control does work. Even when it's included correct in the ROM. Reinstalling Volume Control after flasing using a CAB does work strange enough.
- The sound settings panel won't close after changing sounds.

ROM's I've tried to personalize:
- Panosha
- TOR (SubZero)
- SwiftBL
- VIC Lite
- And probably a few other ROM's I managed to extract (using the kitchen).

I've read some threads about the same problems but they seem to be part of a ROM thread instead of a specific "cooking thread". That's why I started it here.

Do you experience the same problems or do you have some good ideas than please let the rest of us know :)

[iXiR]

I have the same problem :(
Everything seems OK, except the damned sound configuration.
If someone has an answer, we would appreciate it very much.
Thanks in advance...

[mccune]

Thanks for you reaction. Concerning the Volume Control, there is a way to get this to work. Just add a CAB that you call using the config.txt.

It's not ideal but it should work.

Unfortunately this procedure can't be repeated for the sound setting panel :(

[iXiR]

I played with it a lot and even if I do nothing with the ROM, this sound config problem occurs. I extract the ROM and then rebuild it without modifying anything. This looks like a kitchen problem I thought.
I use Surface Kitchen v1.01. You another one, so this is a little confusing :confused:

Edit:
Maybe we can do the same without using those settings but direct in the registry?
Someone knows those keys?

[mccune]

Been using Kitchen 1.0.1 for a couple of days now as well. Updated the programs that were out of date. Did not help.

[iXiR]

I also get always this error, could it be the cause?

[tararura]

I also get always this error, could it be the cause?

HI iXiR
I also get the same error every time. I can not even cook the packages made with package creator. Some times I succeed but at the end it saye User.hv / custom.hv not found. Any idea?
thanks

[anja31]

HI iXiR
I also get the same error every time. I can not even cook the packages made with package creator. Some times I succeed but at the end it saye User.hv / custom.hv not found. Any idea?
thanks

Well, most of the times this fault is there, its a mistake with your new or edited rgu file like \\ or forgotten empty last row.

regards
Anja31

[udayrulz]

I recommend you guys try cooking the 1.93 official ROM .., i cooked a personal one for me .. no problems at all :)

[duttythroy]

I also get always this error, could it be the cause?
this error is because you also have xip directory already listed in ur kitchen, so when the operation reaches that part of extracting the xip it dumps the xip and .dsm a.rgus, so basically a duplicate I dont use this kitchen but you can always press y to overite all

[Caspertje19]

- The sound settings panel won't close after changing sounds.

Try adding this one to your registery:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001


reset and you will be able to change the ringtone/press ok on your sound settings

To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM

[mccune]

Thanks will try that one as soon as I can.

Had one crazy thought. Since there are some replies from some real cookers here I was wondering about the next thing.

At the moment I always select option "1" in my kitchen. So I don't rebuild it (option "2"). It shouldn't but is it possible to have more success when using option "2"?

[ChiefmasterB]

I tried all variants....

select 1 (yes) -> Access denied
select 2 (no) -> the message will appear for a lot of files... even when you always select 2 the ringtone panel won´t work
select 3 (all) -> access denied

So IMO it has no impact, which option you take...

[mccune]

I choose "1". I just want to cook the ROM.

[ChiefmasterB]

Ah.. now I understand what you mean... the question at the beginning...
of course you have to select "1"...

I talked about the overwriting question (screenshots in post before) :)

[GriFolle]

First of all: thanks for this thread...I was going crazy with this issue..!
Has anyone tryied the reg.key posted before?

PS: @maccune...did you tryied to recook swiftbl?! How?! Is it not a protected rom??

[mccune]

Might be wrong about SwiftBL. Tried so many that I could be mixing them up :)

Tried so many because I hoped there would be one that would work just fine.

If it was up to me I'd use TOR v5 since it's basic and still a Diamond build.
Also the cooker told he didn't mind if people would use his ROM as a base ROM for your kitchen ;)

[geistteufel]

this error is because you also have xip directory already listed in ur kitchen, so when the operation reaches that part of extracting the xip it dumps the xip and .dsm a.rgus, so basically a duplicate I dont use this kitchen but you can always press y to overite all

Hi dutty, what do you use to cook and protect your rom ? a made home version ?

[GriFolle]

Sorry, wrong thread...

[ChiefmasterB]

Try adding this one to your registery:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001


reset and you will be able to change the ringtone/press ok on your sound settings

To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM


Wohoooooooo!

It works... really great... perfect...

I also was going crazy to this issue....

now its solved.....

thx a lot.....

BUT: Another question: How can I add this as RGU File to ROM?

[mccune]

I would do this like:

- rename RGU to REG
- use the tool REG 2 XML (http://forum.xda-developers.com/showthread.php?p=2238473)
- Then add an extra line to your config.txt where you call the XML file

[TekTonik]

Wohoooooooo!

It works... really great... perfect...

I also was going crazy to this issue....

now its solved.....

thx a lot.....

BUT: Another question: How can I add this as RGU File to ROM?

I was facing this probleme to and make me crazy also, I have not tested this but could be the solution indeed as I seen that these registry keys was not dumped from cooked roms where it was in the official ROMs

[iXiR]

Try adding this one to your registery:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001


reset and you will be able to change the ringtone/press ok on your sound settings

To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM

Woohoo, it works :D
Thanks man.
I made a cab file which I will let install with the customization after flashing. Or it can be installed afterwards ...

[mccune]

I've got the feeling there's something wrong with the rebuilding part of my kitchen. Like mentioned before the Diamond\Raphael volume control is not working right.

Now we have a small solution for the sound saving problem. But I still wonder why it's broken after starting and rebuilding the ROM. The same with the volume control.

Did anyone manage to re-cook a ROM with a working Diamond or Raphael volume control? If so could you provide us with a link to the kitchen which seems successful for you?

[ChiefmasterB]

Hi,

I use Vic 2.5 LX ROM... everything fine....

but I left out the volume controll of diamond of raphael....
I just use the windows build in volume control...

kitchen is standard surface kitchen from this forum...

[mccune]

@ChiefmasterB

Thanks again for your answer :)

To quote myself:

I tried mixing up the latest Raphael tools with my current kitchen.
Guess what, after rebuilding the ROM I finally managed to keep the volume control to work.

Now don't get mad, I don't need the volume control LOL
But the frustrating part was that the kitchen didn't seem reliable. When I add packages it should also cook them right?

Thanks anyway! The cooking continues.....

[iXiR]

I cooked several ROM's and had once a problem with adding packages. After deleting all files and extracting the kitchen again the problems were gone.
I use surface kitchen: http://forum.xda-developers.com/showpost.php?p=2392286&postcount=3

[mccune]

Updated my apps with the link you provided. Thanks for this.

A bit off topic. But I think the TS don't mind :)

At the moment I'm thinking of two scenarios:
1. Cook a ROM with all my personal favorites.
2. Cook or use a clean ROM and install everything using SASHIMI

The big pro for the second option is that you can update each application separately without hard resetting your device. Or using extra space since you install the update next to the application that's in your ROM already.

Strange there's no topic about this yet. The biggest problem would be creating all CAB's from the packages. But then again this is a one time operation. After this you just update the CAB's with the changed files.

....just an offline thought...

[mondilv]

In Diamond package Volume start by TaskManager (see rgu)
In Rafael - by autostart.

I use "unuversal" way :
[HKEY_LOCAL_MACHINE\Services\HTCVOLUME]
"Dll"="HTCVolumeControl.dll"
"Order"=dword:0000000c
"Index"=dword:00000000
"Info"=dword:00000000
"Prefix"="VOL"
"Module"="\\Windows\\HTCVolumeControl.dll"

And don't forget to disable another ways in rgu files (TM or VolumeControl)

[iXiR]

Updated my apps with the link you provided. Thanks for this.

A bit off topic. But I think the TS don't mind :)

At the moment I'm thinking of two scenarios:
1. Cook a ROM with all my personal favorites.
2. Cook or use a clean ROM and install everything using SASHIMI

The big pro for the second option is that you can update each application separately without hard resetting your device. Or using extra space since you install the update next to the application that's in your ROM already.

Strange there's no topic about this yet. The biggest problem would be creating all CAB's from the packages. But then again this is a one time operation. After this you just update the CAB's with the changed files.

....just an offline thought...
Option 2 is my favorite too. So it is possible to keep the ROM clean and updates are much easyer and you don't have to cook again if there is new or updated software.
Shall we start a project for this ?

[mccune]

I'm afraid this is a bit to personal and would create a chaos thread... ..you would have to create a CAB of all the packages there are. A lot of them are already created by others in the OEM Packages thread, but still it would be hard to keep it organized I'm afraid.

Of course you could give it a shot. I've got a lot of CAB's already but the hardest one to find is the Diamond Dialer. Maybe we can share some. Just PM if you want.

This brings me to the next idea. Maybe create a thread called "Post your Package to CAB wishes here"?

[GriFolle]

I'm OT too, but I would give you the answer mccune:
Look HERE (http://forum.xda-developers.com/showpost.php?p=2536734&postcount=2) for all cabs you need...
For the diamond dialer you have to download the "Videotelephony" cab (infact Swtos had combined videotelephony and phone canvas packs to make it). There are 2 versions of this: the first you can see is the "normal" one, the second one has got inside it also the battery icon improved with the percentage feature...
Enjoy it! ;)

[mccune]

Found out that Swtos indeede combined the PhoneCanvas and VideoTelephony package. A bit confusing. About the color battery, I use my own modified white battery ;)

[pulp]

using Surface Kitchen 1.0.1 @ http://forum.xda-developers.com/showpost.php?p=2392286&postcount=3

i also noticed this problem when trying cook custom roms, however if you extract one of the stock 1.93 roms with the kitchen then look at the file ROM\XIP\boot.rgu and compare it against boot.rgu from a custom rom using something like WinMerge, you will notice the boot.rgu from the custom rom is missing this section at the end of the file:


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Index"=dword:00000001
"Prefix"="DRM"
"Dll"="lsomacore.dll"
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\L sFilter]
"Order"=dword:00000001
"Dll"="LSFILTER.dll"
[HKEY_LOCAL_MACHINE\Init]
"Launch98"="TimeWizard.exe"


add it at the end of your custom rom boot.rgu and problem will be solved.

[mccune]

Nice find! Thanks for sharing :)