yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 Themes and Apps] uzi94:
Can anyone make any different elements like C4 or something else that explodes, because the ones they have now arent that fun....

Uploaded the original file.
[XPERIA X1 Themes and Apps] uzi94:
anyone????
[XPERIA X1 Themes and Apps] sverweij:
Dude you're asking people to modify a game especially for you and you're surprised not everyone's jumping in to get it done? its only been a day since your first post, take it easy..maybe suggest it to the guy who made it?
[Networking] ali-bb:
please can somebody explain to me how to do this, o2 said my phone wasnt compatible but im sure it is right?

thanks
[G1 Android Development] felix88d:
WHAT can i do to get it back to nomal. i backed up my g1 but it keeps going to fastboot screen. i just want it back to normal or factory. PLEASE HELP ME!!!
[G1 Android Development] lbcoder:
What is the device? Have you installed anything non-stock to it (i.e. modified firmware)? Have you tried writing a fresh system image? Have you verified that you don't have any stuck buttons (back button, camera button)?
[G1 Android Development] bigballa:
the camera button being stuck could be it

try to turn on ur phoen with the back case off

if you have isntalled any CF then reinstall those through the recovery menu...
[G1 Android Development] felix88d:
i installed cupcake and well i didnt like it so i tried to reinstall my backup. but for some reason it doesnt let me. also i tryied nandroid v2 but when i write the files it says failed :(
[G1 Android Development] bigballa:
what are the steps that you are taking?

write them out so if i or someone else notices a problem we can address it

be detailed
[Touch Diamond, MDA Compact IV General] ali-bb:
please can somebody explain to me how to do this, o2 said my phone wasnt compatible but im sure it is right?

thanks
[Touch Pro, Fuze ROM Development] dwmackay:
Greetings,

It seems like the talented experts in this forum are making it easier for everyone to build Custom ROMS. As such, I think many of us are trying this for the first time with the excellent Kitchens that show up on the forum. I thought this might be a good thread to ask noob questions so we do not clutter up the ROM specific treads with our general, how-to noob questions. Most of the ROM threads are cluttered enough.

We should always try the search function, but sometimes the answers are not as apparent or as clear as we would like. So here is a venue to ask for help from the pro's.

Doug M.
[Touch Pro, Fuze ROM Development] dwmackay:
Start Menu Organization

So here is my first question for the pros. How do I clean up the start menu in a ROM? Using the 21501 B4 kitchen from DaG and the Erviuskitchen tool, I can easily click the items I want, but many ROMs have all of the apps neatly organized in the start menu. How do I do that?

Thanks for any advice.

Doug M.
[Touch Pro, Fuze ROM Development] hilaireg:
Great idea, here's to hoping it catches on. Eventually, you may want to change the title of the thread to something [FAQ] Commonly Asked Questions, [Q&A] ROM Cooking Techniques, etc. Could be a great candidate for the Useful Links thread (i.e. sticky).

:)

On to your question ...

There are several methods that can be used to get shortcuts over to the Start Menu. One method is to copy .LNK files from the .\Windows folder to the .\Windows\Start Menu using a file called INITFLASHFILES.TXT.

Another method uses a .PROVXML file to perform copy operations, once again, .LNK files are copied from the .\Windows folder to the .\Windows\Start Menu.

Some chefs may choose to leave the processing actions in each package, others prefer to consolidate shortcut processing to a "master" package.

HTH,
[Touch Pro, Fuze ROM Development] jug6ernaut:
This doesnt really answer his question :P hehe. He is asking how to move files that already in the startmenu.

As fare as i know there are 3 methods that you can use(i know there are more but these are the ones i know of).

1. Via program that will move them...like NueLinks

2. Via proxml, tho proxml's are very complicated and one mistake will kill the whole proxml.

3. & Easies way imo is with the use of MortScript, which is what i do.

Just use a mort oem or install mortscript via autorun then exec the mortscript to move the files. here is an example of hte mort command.

If ( FileExists( "\Windows\Start Menu\Programs\Office Mobile\Start_Icon_Office.lnk" ) )
Move( "\Windows\Start Menu\Programs\Office Mobile\Start_Icon_Office.lnk","\Windows\Start Menu\Programs\Programs\Office","TRUE" )
EndIf

first you have the If which checks to see if the file exists, if it does then it Moves it to a set dir. If the file is not there it just moves on to next function in mort file.
[Touch Pro, Fuze ROM Development] hilaireg:
You are correct, hence the:

... had hoped a seasoned chef would jump in.

;)

Cheers,
[Touch Pro, Fuze ROM Development] jmckeejr:
You also have to remember that some if not most of the files are write protected, so if you use a mortscript(I also just started using these too) you have to set the file property so it is not read only. This might only apply to links you want to delete, but I have a script that covers most of the common links in the programs folder. I have a cab install my links that have custom icons, so if it does not overwrite the original you will have 2. I like my programs all in folders and organized, so I delete all of the links inside of start menu\programs\ an just use my cab with custom icons to install links. I've attatched my script for Da_G's 21042 kitchen(I actually only use the SYS\XIP) that you can use as a base. It also does some cleanup of extra files, but you can delete that part if you dont need it. I started out by cooking the ROM, flashing, then I go through and write the script to cover all the links I need changed or deleted. Then I test the script before cookin it into a ROM, this way you know what is going to happen ;) I have a different way of writing mine tha Juggernaut, but still effective.

Just have it run near the end of your configuration as:

EXEC:\windows\cleanup.mscr

Also, a good way to do it which is probably what a pro would say is to get to the root of the shortcuts in the initflashfiles.dat file. It stores where shortcuts go and a lot more. I am actually going to give this one a try next time, as I just now remembered seeing those entries in there...duh. But it does not define where all shortcuts go, as there are plenty of provxml's and initflash.txt files. Lets see what the seasoned cooks have to say though, as I am just a young padawan myself ;)
[Touch Pro, Fuze ROM Development] Farmer Ted:
I've done it using a combo of setting things I want in the start menu in the initflashes in their packages and removing the stock stuff out of initflashes.dat (found in one of the oems, oem_lang_0409, I think). I don't believe it's absolutely necessary, but if you edit the initflashes.dat, afterwards you should open it up with a hex editor and remove the first two bytes (check before and after, and you'll see that there are two extra new bytes at the beginning after the edit). Anyway, this file has stuff like the phone, messaging and contact links in it that always appear in start menus.
[Touch Pro, Fuze ROM Development] rgb-rgb:
If you edit the initflashes.dat in the ervius visual kitchen (the one from Da_G's 6.5 kitchen), do you still have to edit out the first two bytes with a hex editor?
[Touch Pro, Fuze ROM Development] Farmer Ted:
I don't think you actually need to do it; I just read about it in the blackstone cooking thread. Apparently, with some of the older devices you had to do it, but you may be able to let it slide with the newer ones. I downloaded a hex editor and wanted an excuse to use it, so I personally deleted the two bytes when I edited the .dat file. I'm using At0m's kitchen; can't speak for Da_G's. FWIW, it's a real simple thing to do (heck, get the hex editor package and you can do it on your phone).

Oh, and jmckeejr's cleanup script is very nice. Glad he explained about the first part (setfilattribs....). You need to do that if you want to delete most links or .txt files, as a lot of them are read-only. (I'm also a noob, lol, but figured I might as well contribute where I can. Hopefully the pros will answer the tough ones.)
[Touch Pro, Fuze ROM Development] monx®:
Another way is using the *.provxml like :

<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="\Windows\Start Menu\Programs\Adobe Reader LE.lnk" value="\Windows\Adobe Reader LE.lnk" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>

to sort :

<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="\Windows\Start Menu\Programs\[B]Whatever[/B]\Adobe Reader LE.lnk" value="\Windows\Adobe Reader LE.lnk" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>

I hope this helps but I dont use this way :p (i hope this will clear a bit for hilaireg's post)
[Touch Pro, Fuze ROM Development] jug6ernaut:
what do you use monx? teach us ur ways! :P
[Touch Pro, Fuze ROM Development] monx®:
nothing special mate, just the oldest method. initflashfiles.txt in each oem folder. So I only use minimum *.provxml (I also removed autoshortcut.exe :p )
[Touch Pro, Fuze ROM Development] jug6ernaut:
ahh ic :) (i hate proxml's and will never touch them :P ). it toke me a while to figure out that autoshortcut.exe was putting .lnks in the startmenu(many headakes in the process hehe).

Glad to see your still around and spreading ur wise wisdom :D.
[Touch Pro, Fuze ROM Development] hilaireg:
I prefer to keep the shortcuts with the respective package ... makes it easier to hand-off the package to other folks who might like to use it.

I have obtained packages where INITFLASHFILES.XML contains the operations, others where .PROVXML contains the actions, and then others where they use a hybrid of both. In my custom configuration kitchen package, I almost exclusively use .PROVXML to apply registry settings or changes to attributes on files.

@dwmackay:

So there you have it, a comprehensive answer to a "simple" question. Some excellent (seasoned) masters have shared their experiences and recommendations. I've picked up some great tips and I'll be interested in reading the responses on the next question(s).

What an awesome community!

:)
[Touch Pro, Fuze ROM Development] dwmackay:
Thanks for the detailed answers. I may have concluded that this is above my pay grade. I'll read through the details more carefully and see what I can figure out.

Thanks again,

Doug M.
[Touch Pro, Fuze ROM Development] da_jojo:
i'd go for monx way allthough i see no difference in the two pieces of code , it is the best way.

that way you keep the oem-packages clean and won't end up with unnecessary shortcuts.. besides u wont need install mortscript
[Touch Pro, Fuze ROM Development] jmckeejr:
Even if I didn't use the mortscript way, I would cook it in. Mortscript can be a very powerful thing, and its only a little more than 1MB so good to put it in either way. I personally use Sashimi to autoinstall and import Registry and what not, so I cook it in and all of my programs and settings are auto. I can flash a ROM now, and have it set up within 5-10 minutes(after initial customization runs). Sashimi relies on mortscript, so good to have it in there. You can add Sashimi compliance

and

UC, so why not add them both? I would try a lot more ROMs if they were Sashimi compliant, and I'm sure others feel the same. Just a headsup for cooks. It takes almost no extra effort to add one line to your config_operator.txt, and include a mortscript in your operator Package.

This is a good thread. I have a question, not really a cooking question more of a preference question. What PagePool have you found to be the best for you? I tried a bunch of different settings, and haven't found a huge difference so I usually set mine at 16-18MB which leaves more free RAM than say 24MB. I there any relation between pagepool and battery usage? I found my battery life to be better when pagepool was set a little lower, but wondering how others feel about it. Stands to reason that a lower pagepool would mean a smaller memory footprint therefore better battery. Am I wrong here?
[Touch Pro, Fuze ROM Development] jug6ernaut:
500kbs if u use an oem :), i <3 mortscript.

umm i recently heard 16mb pp is the best from benchmarks.
[Touch Pro, Fuze ROM Development] 12aon:
The difference is the "whatever" part. Can't say I'm a seasoned chef but messing with provxmls is really not that hard as long as you don't move or rename them. I've been cleaning up my entire start menu every time da_G released a new kitchen and I made a folder with the files that I have changed before and need to insert to get a clean startmenu:

- initflashfiles.dat

- mxip_HtcApps_translation.provxml (this is for the settings menu)

- mxip_MyPhone_100.provxml

- mxipupdate_office_100.provxml

- mxipupdate_onenote_100.provxml

- mxipupdate_PACKAGE_Raphael_CAMERA_0409.provxml

- mxipupdate_windowslive_1.provxml

- mxipupdate_windowsliveim_1.provxml

, 12
[Touch Pro, Fuze ROM Development] hilaireg:
Same here,

I have a '01_PACKAGE_CUSTOMIZED' where I have a copy of the OEMOPERATORS .provxml, .DLL's or .EXE's that should take precedence over those in a package, and custom images/sounds.

PackageBuildOS 5.3 processes the contents of this package before the others ('01_') ... not sure if this will still work /w the New Style Kitchen as I haven't tried it yet.

Added benefits include:

- Not messing around as much with other packages

- Not messing around as much with OEM and SYS

- Quick to test a .DLL/.EXE for compatibility during a test ROM cook

It doesn't address configuration entries that appear in multiple .PROVXML's (or .RGU's) but it sure helps me track down the culprit if I see that my changes aren't present.

Cheers,
[Touch Pro, Fuze ROM Development] jmckeejr:
Thats not a bad idea. Then if you import a new SYS, there would be less headache. I know when I first imported the 21042 SYS, I had to cook and flash a few timeds before getting rid of all the extras.

Next question, how can we have a splash automatically cooked in? Someone had said to edit the "TouchPro.htcrtproj" file, but don't think its workin for me. I've been using the NBHUtility to break down the .nbh and recompile the os.nb and splash.nb. I have tried to edit the project file as follows.

[Buildrom]
Device=Diamond
ModelId=RAPH*****
CountryId=11111111
VersionId=Touch_Chrome_RC3
LanguageId=WWE
Sect_0x400=False,"OS.nb"
Sect=_0x600=True,"D:\Full Chrome Kitchen\Splash\newest_splash.nb"

Can you tell me what I'm doing wrong? Or the correct way to do it.

EDIT: Now that I look at it, looks like I got an extra = in there. Oh well, if I hadn't posted then I might not have seen it.
[Touch Pro, Fuze ROM Development] hilaireg:
Nice that you did ... hadn't realized that could be done that way - figured it would require a subsequent 'Splash Only' flash.

:)
[Touch Pro, Fuze ROM Development] jmckeejr:
Ok, I have a question. Not sure if its the right place, but I figured a forum full of chef's would have an answer. So I have been doing some cooking as of late. I got my 20771 buildrunning sweet and the battery could last me all day listening to music through bluetooth. The only thing I was missing was the full notification bubbles from Topaz/Rhodium. Today I was feeling brave and switched out some parts from 21042 to 20771.

I now have the notifation working(see screens), but I don't get the nice icon in the notifications that I did from 21042. Can anyone provide some info on maybe any other depedent .dll's or .exe's? I also thought this info might be interesting to anyone who wants the notifications without the 21000+ build. If I can get this working, I will be so,so happy with 20771. The ROM is also now much more responsive, but might be due to increased pagepool. Thanks in advance-the noob cook;)
[Touch Pro, Fuze ROM Development] hilaireg:
Attributes On Files - OEM/SYS/Packages

What is the list of attributes *that must* be applied (per filetype) to the files found in the the OEM, SYS, and Packages folder?

During some of my testing I discovered that if I remove *all* file attributes (A, S, R, H, etc.) from files in the OEM/SYS/Packages folder, the final cooked ROM is completely broken.

Cheers,
[Touch Pro, Fuze ROM Development] Da_G:
I know for sure the .vol's need +s (maybe +h +r, can't remember)

provxml's may also need to be +s.

i think those are the only 2 requirements.. if i recall correctly..
[Touch Pro, Fuze ROM Development] jmckeejr:
Also wanted to add that with the notifications cooked in the way I have mentioned above, that you can now choose snooze for different amounts of time. As opposed to the snooze with current 21xxx+ builds which have snooze, but only allows for 5 minutes. Must be something that can be used to change the behaviour on newer builds that we can learn from this. It is most likely the part that I am missing which shows the icons in notification bubbles. Anyone interested in looking deeper into this? I know that a lot of people have moved onto the 6.5 stuff, but some of us prefer an HTC device over a Windows device.

More screens:
[Touch Pro, Fuze ROM Development] hilaireg:
What packages are you finally using to achieve the pictures in your last post?

I'm willing to forgo the icons for selectable options.

;)
[Touch Pro, Fuze ROM Development] Captain_Throwback:
There must be a way to have both, right? It looks like the main difference is the soft keys - with the newer builds w/the Notification Enhancement, the LSK is "Snooze" (5 minute duration only), and the RSK is "Dismiss". Its that "Menu" option that we're missing. Is that something that would be in an .mui file? I wonder if there are just entries that need to be added to make it work?

EDIT: I know there's that registry key to use the "DefaultUI" that brings the menu options back (see below), but usually that's at the expense of the enhanced notifications. I wonder if there's a combo of reg keys that'll allow the default menu options, along with the enhanced notifiations?

[HKEY_LOCAL_MACHINE\System\Shell\Notification\OEM]

"UseDefaultUI"=dword:00000001

@jmckeejr

What does your reg look like at the above key? There's also a subkey for "Reminders" that has the simple enhanced notification menu options. Maybe the answers are in there?
[Touch Pro, Fuze ROM Development] hilaireg:
Agreed,

Hopefully 'jmckeejr' can post up a package set for what he currently has working.

:)
[Touch Pro, Fuze ROM Development] 12aon:
Anyone know where the "midgets" text is located, supposed to me an image file in oem somewhere but I can't find it, 12
[Touch Pro, Fuze ROM Development] hilaireg:
@12aon:

LogoMsg.bmp

Factory file here:

http://xdaforums.com/showpost.php?p=3544944&postcount=601
[Touch Pro, Fuze ROM Development] jmckeejr:
I have tried it both enabled and disabled. Still working either way. I posted my oem for the notification manager in repository, and the rest was just replacing a couple files in SYS from 20771 with parts from 21042. Specifically, shell32.exe and the gwes.exe. But I also tried to add the ddi.dll from 21215 I think. I will look again later. I am not sure what part of 20771 you would need to have the selections in a newer build. more to come...

EDIT: was wrong on the DDI.dll. Used that one in 21042. Anyone tried adding it to 20771? Was feeling brave earlier, but now I gotta get set back up for work in the AM. What about NK.exe? Would this be interchangeable? Feeling kind of dumb right now because I searched my kitchen and cant find it anywhere, but it is definitely on my device :confused:

The mui thing is partly right, as the only way I was able to get this far is because I found somewhere that notificationlayout.mui is somehow tied into the shell32.exe.

I guess if I can find the right part to make notifications work with icons it might resort to the 5 minute snooze, but if it does then theoretically we could use that part from older build in a newer build to get the same menus right? Dont worry if this confused you, looking at it now I confuse myself sometimes LOL ....sleep is your friend

EDIT2: What is mxip_notify.vol?
[Touch Pro, Fuze ROM Development] hilaireg:
I have those moments too ... like right now for example, how do you display the Notifications panel. :rolleyes:

http://xdaforums.com/showpost.php?p=3732546&postcount=23

* EDIT 1 *

Figured out where the Notication menu was stashed away ... learn something new about this device every day.

* EDIT 2 *

NOTIFY.DLL & NOTIFY.DLL.0409.MUI corresponds to 'UseDefaultUI'.

Would be nice to adjust that MUI to sport the same coloured icons as the TP2 ones I am using ... ;)

* EDIT 3 *

MXIP_NOTIFY.VOL = Database

http://msdn.microsoft.com/en-us/library/ms885373.aspx
[Touch Pro, Fuze ROM Development] Farmer Ted:
Well, speaking of feeling dumb, what exactly is the difference between an XML and a provisional XML? I'd like to put run an XML during customization (to change the taskbar color). I used reg2xml to convert HKCU\Software\Microsoft\Color to an XML, and the output is a provxml. Is it ok to just change the file extension (then run the xml in config_operator)? Comparing it to another XML file I have, it pretty much looks the same, but the indents are a little smaller (I have no idea if that matters or not). I just left it as a provxml and put it in the operatorpkg OEM, but did not get the desired effect. I can easily make an XML or the reg key using QuickCab, so it's not a big deal, but I'd like to know what the advantages/disadvantages of using XML's vs. provXML's are.
[Touch Pro, Fuze ROM Development] hilaireg:
You're good to go - a .PROVXML and a .XML construct is the same. If you're planning on using FDC Task Manager to test your .XML/.PROVXML, you'll need to add the .XML header info - I usually use the first line on an OPTION.XML - and then temporarily rename the .PROVXML to .XML.

ANSI/Unicode supposed to be supported; I find however, that ANSI seems to be most predominant.

To recap, build your file as a .PROVXML and then add the .XML header line during testing. Once everything is good, remove that first line and you're done.

HTH,
[Touch Pro, Fuze ROM Development] drazah101:
I have a query about auto setting up cabs on the auto customisation part.

I am using daags 21222 kitchen and i was wondering where and how i put the Config.txt and the .cabs i want to auto install on startup.

Thanks !
[Touch Pro, Fuze ROM Development] Farmer Ted:
Haven't used that kitchen, but look in the Operatorpkg OEM in the OEM folder (I think that's the name). Drop the cabs in there (you'll probably see some in there already, and provxml's and the like). Then add the install command in config_operator.txt.

Awesome, thanks! I ran the test (didn't have to change any headers, just changed the extension) and it worked as it's supposed to.