I need some help debugging the kitchen with the touchflo files.
For those who are sent the new kitchen; as you test and find solutions, please post what you did.
I wanted a sperate thread for just these specific objecives.
Here is the objectives:
To retain the ability to build a ROM with or without TouchFlo
To have only ONE seperate camera package that will work in any configuration
To allow portions of the touch software to work seperately should TouchFlo not be installed
I know there are other threads dedicated to debugging the touch software, however this is targeted at just the kitchen integration.
Current issues (v2):
Streaming Media isn't showing up in Programs, won't open.
Speed Dial hasn't been confirmed working or not.
No images for Beam - still need pictures!!!
Windows Live won't connect. Cab fixes issue. Need to find missing entries
Black Keyboard doesn't show numbers across top row. Need to find setting.
The power button will put phone into "standby" mode (basically screen and Wifi off), but won't power down.
318
I'll be glad to test. I was working on a 318 Kitchen but didn't get very far.
Too many Duplicate files.
Going back to work on my own kitchen I was much further along than what you have here.
My suggestions:
1) You should at start by deleting duplicate files. I can build a rom and flash it with my kitchen, I can't build with yours w/o getting one dup file error after another.
Please update, I will try to devote some time to your kitchen.
Thanks
NP. I'll update shortly.
My Files
I deleted dup files in my kitchen but I think I deleted one to many, now I can build, and I can flash using shelltool but it gets stuck at splash screen. Damm where did I go wrong??? I feel like a dumbass!
Hopefully this one will work a bit better. another 30 mintues till it's up.
The boot issue is probably related to the files in the OEMAPPS folder. There are some dll's in there that I found are super sensitive to this build - too bad I wasn't more careful in documenting what they were.
Documenting.
Started documenting now! Too much going on now not to, especially after my last mistake.
Test
So have you actualy built and started testing a rom with your kitchen?
I've been doing that for days... but I've tried a number of different combinations and this one seems most promising - though by no means is it ready. 1413 has by far been the easiest, but I still believe the 318 is the best choice.
I'm gonna be out until Monday night, so this is my last attempt for a few days
I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.
Whiterat said:
I have 318 with touchflo working.
Keep the original OEMAPPS im afraid, literally just the touchflo components (Audiomanager,etc) and then use recmod on touch.dll and throw it in OEMDRIVERS.
Ive just finished my refined version of the DOPOD touch rom, very well tweaked, it is as close to OEMWizard as it will ever get.
Going to give that a test burn tonight hopefully.
I will post my OEM folder for 318 if you need it.
Click to expand...
Click to collapse
If you could, it would be much appreciated. Anything to help get closer to a fully functioning setup
Ok, so i tested the oem folder from the reTouched Beta thing. I included everything in there but my problem is that TouchFLO does not function the way it is supposed to. With what you guys are doing, have you verified that TouchFLO even operates correctly?
I thnk the touch flo isn't all its cracked up to be..I ran the reTouch wasn't a fan..its not as fast as any rom..only thing I like is the dialer and the cube
I actually have a good feeling about it. I ran the french rom for a couple days - and other than not knowing most of what it said (glad I know the OS and took 2 years of french in high school) I was very pleased with the performance. Specifically the speed at which the screen "rotated", responsiveness, and how quickly the contacts scrolled on the screen was impressive. Enough to keep me interested well into the night
so matt, think you can make a cab from it? the cube that is lol.
Here you go:
http://rapidshare.com/files/40068930/OEM.rar
Click to expand...
Click to collapse
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
So if what you are saying is true I should be able to create cabs from the correct?
AFAIK It wont be possible due to the touch driver not being replacable, you might be able to rename touch.dll and then update the registry entry.
cleaning up
Whiterat said:
Here you go:
Works perfectly but does need some cleaning up to fit your needs (Whiterat and OEMOPERATORS folders)
Click to expand...
Click to collapse
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!
hanzieman said:
Hello, can i just copy this oem-folder to the kitchen and then remove the whiterat-folder. Which folders do i also need to delete to flash the rom?!
Click to expand...
Click to collapse
For what I see whiterat folder are some reg tweaks that you'll probably use anyways, and as far as folders to remove it might be less of a hassle to simply add the packages that you use that are not there.
Related
I have been attempting to add Interenet Calling to Faria's WM6 ROM by adding the necessary files and registry changes and re-cooking the ROM but I am getting nowhere fast. I have managed to add some files to the original ROM, make a couple of registry changes fine and change some settings in the initflashfiles.dat file to remove some shortcuts I don't want and I can get this to work fine, however re-adding the IP Phone stuff is a bit more of a task.......
I have extracted the files (or modules) from the MB ROM and added the regsistry changes and the ROM cooks just fine. When I flash the Wizard though it completes sucessfully and then reboots. I get the 1st splash screen but then when the 2nd splashscreen should appear I get a white screen. The Wizard is working as I can hear the bleep when it asks you to 'tap the screen to set up the device'. It also powers on and off OK, but I only ever get this white screen.
I have tried this about 4 times now and I am convinced the registry changes and required files are correct, but each time I get this white screen. Any ideas?
Andy
http://forum.xda-developers.com/showthread.php?t=290786
Read this... especially towards the end.
trojan9x said:
http://forum.xda-developers.com/showthread.php?t=290786
Read this... especially towards the end.
Click to expand...
Click to collapse
Already read it..... I can get Internet Calling back if I launch the VoIP.CAB that is included in that thread after installation, however I want these to be integrated into the ROM like they were originally (Faria has removed them). As I said I have had some sucess with adding other files and other registry changes it is just this bit that I am stuck on.
I did manage to get a bit further but ended up with a corrupt Today screen, no idea what happened there though
Andy
What are you stuck on?... you said you didn't have it, but now you said you can get internet calling... what exactly are you trying to do?
Faria has said that his rom takes up almost the entire space alotted. Have you tried removing some files from the rom to clear up room for the VoIP files?
trojan9x said:
What are you stuck on?... you said you didn't have it, but now you said you can get internet calling... what exactly are you trying to do?
Click to expand...
Click to collapse
I want to restore the Internet Calling option in Faria's WM6 ROM - pretty simple to understand really
I can add it manually via the VoIP.cab file but this obviously takes up RAM and can be removed via 'Remove Programs'. I would like to add the files that are missing and make the necessary registry changes then re-cook the ROM. I would prefer to keep Faria's base ROM.
I haven't tried removing anything from Faria's ROM so far, I didn't realise it was near the limit - I thought we had 128MB to play with on the Wizard, are we near that already?
Andy
Listen.. that cab only does registry fixes and puts in the NECESSARY files for the current voip functionality. it does not install anything that is not needed. Extract the cab and look at the xml file. it will tell you exactly what it does...Pretty simple concept
trojan9x said:
Listen.. that cab only does registry fixes and puts in the NECESSARY files for the current voip functionality. it does not install anything that is not needed. Extract the cab and look at the xml file. it will tell you exactly what it does...Pretty simple concept
Click to expand...
Click to collapse
Yep, already done that, hence my original post.....
I have added the necessary registry changes/additions and proof-read them several times, however once the ROM is cooked and installed the thing reboots, I get the 1st splash screen OK, then the white screen when the 2nd splash screen should appear and that's it.
I will have a look at how bloated the DUMP directory is with the additional files in there and see if I am going over 128MB.
Andy
The DUMP folder is apparently 122MB (128,512,401 Bytes) but is taking up 132MB (139,141,120) on the disk on my PC. Does anyone know if this is too big? If it is what is safe to remove?
Thanks
Andy
Done it.......
If anyone is interested I managed to get Internet Calling back into Faria's ROM.....
What I did originally was correct, however the file (or modules) that are needed for Internet Calling total about 3.5MB, which I think was slightly too much and would make the ROM bigger than 128MB (I think Faria must have realised this when developing his ROM and removed them to save space). I have been through the installed applications and files and have removed some stuff that I don't use. I then re-built the ROM and low and behold it worked first time and Internet Calling is now an option...
It still doesn't work however but that is just because it needs a provisioning XML file from a provider. Hopefully when WM6 devices appear we will be able to extract a provisioning XML file and dig deeper........
And no, the ROM is not available since this is Faria's work and not mine.
Andy
Nice,
I’m new to this and the only thing that I need from WM6 is the “Internet Calling”
I have no ides how to make the voip work. But I fond this at Microsoft.
http://msdn2.microsoft.com/en-us/library/ms898226.aspx
I really would like to test this with my “asterisk server” (http://www.asterisk.org/)
/joad
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
joad said:
Nice,
I’m new to this and the only thing that I need from WM6 is the “Internet Calling”
I have no ides how to make the voip work. But I fond this at Microsoft.
http://msdn2.microsoft.com/en-us/library/ms898226.aspx
I really would like to test this with my “asterisk server” (http://www.asterisk.org/)
/joad
Click to expand...
Click to collapse
I have exactly the same intentions, joad. I've got wm6 on my O2 XDA mini so I can try and connect to my Asterisk server as well!
Let's hope his eventually works.
N
joad said:
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
Click to expand...
Click to collapse
You need to add the following files into the ROM (the 1st 3 are actually modules and are in directories with the same name):
dnsapi.dll
rtcdll.dll
voipphonecanvas.dll
ipdialplan.xml
ringback.wma
You also need to add the registry entries to the default.hv and user.hv that are contained in the '_setup.xml' file from the VoIP.CAB file (or extract them from another ROM that already contains Internet Calling).
HTH
Andy
joad said:
Where did you find the "Internet Calling total about 3.5MB" module?
Or maby you have changed your mind and feel like chairing your ”build” of WM6
Click to expand...
Click to collapse
Joad,
I agree with you. The 3.5 Mb footprint is inflated.
It's only 1.75 MB (remember if you are using recmod when you are unpacking the ROM with viewimgfs, you have two copies of the files that are stored as modules: the module version and a file copy!.
--eluth.
eluth, I knew that somebody out there would have done the right job. Congratulation! Would you mind making your rom available to us?
Thank you
Gio2003
Pleaaaaaaaaaaaaase !!!!!!
There are so many people wanting to do this now - and I have a MAJOR need for this on a Hermes -- I have a solid SIP provider and can get to it with my other apps but integration I can't test ---
I am trying soooo hard to pin this down. I have not found a single ROM yet that has the "complete" add-in of what you mention here.
It would be GREATLY APPRECIATED.
Thanks
gio2003 said:
eluth, I knew that somebody out there would have done the right job. Congratulation! Would you mind making your rom available to us?
Thank you
Gio2003
Click to expand...
Click to collapse
ckolibab said:
There are so many people wanting to do this now - and I have a MAJOR need for this on a Hermes -- I have a solid SIP provider and can get to it with my other apps but integration I can't test ---
I am trying soooo hard to pin this down. I have not found a single ROM yet that has the "complete" add-in of what you mention here.
It would be GREATLY APPRECIATED.
Thanks
Click to expand...
Click to collapse
This .CAB worked on my Wizard with Faria's WM6 real thing ROM that had the VoIP stuff removed:
http://forum.xda-developers.com/showpost.php?p=1147821&postcount=138
I then added the files and registry settings back and re-cooked the ROM.
HTH
Andy
I wanted to get a thread dedicated to getting the applications out of the Touch .nb, and into the Wizard - and specifically the "cube" and "touch" functionality that is the trademark of the new phone.
Please save "oh, I'd like" or "oh, wow" stuff for other threads - this is a dev discussion.
Criteria: Working discussions on what's been done, what are we doing, and what could be done to get the excellent new features to work.
I hope that by sharing information - we can key in on the results much faster then everyone working on their own.
Software Packages
This post is a running list of applications, and their status:
Application............. .Status:
HTC Camera ............. .???
MediaHubMini ............. .???
QuickDial ............. .???
Streaming Media ............. .???
Streaming Player ............. .???
Cube ............. .French rom working, no WWE yet
Dialer Pad ............. .Done
Comm Manager ............. .Done
Today Home Theme ............. .Done
If someone can PM me who's current on this thread, I'll update the remaining items.
.
Kickoff Status
Here's what I've tried so far:
Using the 1413 as a base, I've taken and replaced the OEM folders from the touch build and replaced the 1413 folders -completly. This resulted in the phone self power cycling at the 3rd splash screen.
I've also taken the entire touch build, replaced the ROM contents with the one from 1413 (and I might have replaced the /SYS/OS folder as well - going off memory). This was the most successful, as I was able to boot the phone and get a lot of the touch's functionality. Issues were: SID Lock error, no "touch" function, and button mapping was wrong - only button 1 showed up on settings - buttons.
More info (a little)
Well, to follow up on my note in the other thread. I did pretty much what you did and ended up in the same place.
I did discover that the two other "raw" files in the original leak contained xip contents. I'm not sure why there are two of them, and they contain similar contents. I ran a build using the one I've labeled xip1 and it gave an error about missing build.rgu in buildos. I then ran a build using the one I labeled xip here (which has a build.rgu) and it built and booted, but worked essentially the same as when using an older wizard xip.
Anyway, time for bed now.
PS I tried to upload a zip of the two xip sections but it failed. Forum maintenance I suppose. Maybe I'll try again tomorrow if anyone seems interested.
Edit: Tried again to upload, failed.
I think we should start by the Dial Pad... I think it will be the easy thing to do.
Check this Hermes Rom:
http://wmblack.info/
and this:
http://www.4winmobile.com/forums/hermes-black-rom-support/9792-released-black-iv-shadow.html
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
anichillus said:
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
Click to expand...
Click to collapse
I also thought this... But now we have an official build from ms... I think it is a bit more stable than a ported version (if i'm wrong, please correct me).
@joaosousa:
I tried to port the Dialpad yesterday... But it seemed that I missed some needed files/registry hacks.... Still trying.
Vi
I also think we should keep the official build from ms... It's very stable...
any luck with touch dialer skin?
In all seriousness... the Today plug-ins for the HTC touch are fricking ugly.
Anything new in here?
joaosousa said:
Anything new in here?
Click to expand...
Click to collapse
Ya... I just flashed my wizard... Without the correct XIP partition -> stuck at 87% but bootloader works... so i think i'll get my wizard back
vi
omg... Hope all goes right with your wizard...
For those who want to play...
OK, for those who want to play with the Touch Rom, here's a rapidshare link to download a "working" nk.nbf. I've also included total commander, and a registry editor for those who might want to tinker with getting things to work.
The main issues are these:
1) Pull the sim card before flashing, or you won't be able to to get to the today screen.
2) Since the elf is only a one button machine, most of the buttons do nothing, including the power button. You'll have to take out the battery to turn it off. (Unless you can figure out the registry changes needed to make it work.)
3) Don't worry about setting your timezone in the initial screen. You can set it later from the settings menu.
4) Be ready to flash back from bootloader mode when you're done exploring!
5) I pulled adobe acrobat, catalog, autoupdate. Everything else is pretty much stock. So you can get a feel for what's included, and what you might want to pull for use in the Wizard!
This is OS only.
Have fun!
Rapidshare Link: http://rapidshare.com/files/36574080/TouchROM-nk.nbf.rar
Here's a question to those who have tried it so far: has anyone seen it working, or know which application controls the 'cube' function? Is it the biotouch app?
edhaas said:
OK, for those who want to play with the Touch Rom, here's a rapidshare link to download a "working" nk.nbf. I've also included total commander, and a registry editor for those who might want to tinker with getting things to work.
The main issues are these:
1) Pull the sim card before flashing, or you won't be able to to get to the today screen.
2) Since the elf is only a one button machine, most of the buttons do nothing, including the power button. You'll have to take out the battery to turn it off. (Unless you can figure out the registry changes needed to make it work.)
3) Don't worry about setting your timezone in the initial screen. You can set it later from the settings menu.
4) Be ready to flash back from bootloader mode when you're done exploring!
5) I pulled adobe acrobat, catalog, autoupdate. Everything else is pretty much stock. So you can get a feel for what's included, and what you might want to pull for use in the Wizard!
This is OS only.
Have fun!
Rapidshare Link: http://rapidshare.com/files/36574080/TouchROM-nk.nbf.rar
Click to expand...
Click to collapse
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
anichillus said:
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
Click to expand...
Click to collapse
Yes, understood. I think the fact that it works just as well with either XIP just shows how similar the two machines actually are. Either that, or whoever "leaked" the rom included an appropriate XIP on purpose.
its right said:
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
Click to expand...
Click to collapse
Fully Touch Rom. But it has been restructured to fit inside the partition settings of the Wizard.
mattk_r said:
Here's a question to those who have tried it so far: has anyone seen it working, or know which application controls the 'cube' function? Is it the biotouch app?
Click to expand...
Click to collapse
For me it didn't work. Did you notice a kind of "klick" every 2 - 5 seconds? it sounds like if the speaker are turnend on and off...
Vi
its right said:
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
Click to expand...
Click to collapse
The SYS and OEM folders from Touch, the ROM folder from 1413 (going off assumption here - correct me if I'm wrong )
Okay,
I have had my wizard for about a year now and in that time have flashed countless ROMs without any major problems, but yesterday I came as close as I ever have to bricking my device, and the crazy thing is that I have no idea why. I am hoping that the "real men of genius" here can help me figure out what the freak happened, or specifically what I probably did wrong
Before anyone asks, yes my phone is SIM and CID unlocked and it is a G3.
I recently moved from Core 2.0n to mfrazzz XDA Mobile 6. I really liked it but with mattr_k's easy kitchen and stripped down base I figured I could play with it a little to get some more of the apps and settings I like in it from the get go, and save the space without the ones I don't. I had been playing around with the core kitchen and the first kitchen mattk_r upped so I had a pretty good idea of what to do.
here is what happened as best as I can remember ( I should have taken notes as it was happening but I was too freaked out!)
I created the OEM directory and copied the reg tweaks and packages that I wanted from Pandora's Box (v2). I ran Build OS and selected all and it completed without problem. I ran createROM.bat and no problems there. I went into flashing, built the nbf and flashed. The flash went fine with no hang ups.
When the device restarted after flashing it went to the first splash screen and then stayed white. I left it this way for 10 minutes and then it was still like this I tried a soft reset. It reset fine but stayed white. I then tried flashing back to the original mfrazzz ROM but when it got to 95% the flash tool errored out and closed. The phone was stuck with the progress bar at 95%.
I freaked out a little and then rembered that I still had a copy of wizard love on this computer so I put it in bootloader mode and then flashed that. That got the phone back up. I then tried reflashing my "cooked" ROM. It loaded this time, but the today screen was a white background and some of the today plugins were extremely distorted and it just wasn't right.
I reflashed wizard love, and then reflashed the mfrazzz's original XDA Mobile. My phone is now fine.
Any ideas on what the heck happened.
Just guessing here....did you messed with the splash screens ?
anichillus said:
Just guessing here....did you messed with the splash screens ?
Click to expand...
Click to collapse
Not on purpose, followed the steps above as far as I can recall.
You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking
When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
If you only did the OS, what is the size of your nk.nbf? If its too big it wouldn't have flashed.
BTW: Welcome to the world of rom cooking... I've scared myself a few times
ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!
When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
mattk_r said:
ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!
Click to expand...
Click to collapse
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!
boto said:
You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking
Click to expand...
Click to collapse
well it would definitely be a tragicomedy!! or perhaps a nail biting thriller! I wanted to give as much detail as possible since I hate it when someone posts, "I bricked my device, what happened?!?!?! PLEASE HELP!!!!"
dcdivenut said:
When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!
Click to expand...
Click to collapse
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.
mattk_r said:
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.
Click to expand...
Click to collapse
I don't think I entered WWE for language, but I did everything else, and didn't do anything extra. That is something to try...
UPDATE!!
I am not sure that something as simple as typing WWE in the language field is what made the difference but I did and it worked. On my home computer I redownloaded the kitchen, base and OEM packages.
I first flashed it with nothing added to the OEM folder and it worked
Then I added to the OEM folder and that worked.
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Any help from the pros in getting this up woudl be awesome! Hopefully others will be able to use them as well.
dcdivenut said:
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Click to expand...
Click to collapse
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .
mfrazzz said:
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .
Click to expand...
Click to collapse
SWEET!
Soft key - Check
Time Sync - Check
I found this in the .rgu file in the x-mfrazzz apps. is this for the softkey app or something else?
[HKEY_LOCAL_MACHINE\Services\Stk_service]
"Dll"="\\windows\\STK_Service.dll"
"Description"="STK Service"
"DisplayName"="STK Service"
"Context"=dword:00000001
"Keep"=dword:00000001
"Order"=dword:00000005
"Index"=dword:00000005
Windows Live search - In your OEM folder there are two folders, WindowsLive and WindowsLive_DPI_96. These are both currently also in the SYS folder of mattr_k's base so wouldn't this throw an error? I know I am missing something stupid here.
Ring tones - Is there anyway I can build mp3's into the ROM? I tried placing them in the x-mfrazzz settings folder in my SYS but that didn't work, even though they get built into the windows directory. I looked in the .rgu and there doesn;t seem to be anything about where to place these
PHMReg Edit - I thought I remembered you saying something about being able to export reg settings in the correct format. I was playing around with this and the closest thing I could find was backup. That created a .rbk file but I get gibberish in notepad when I try to open it. My thought process here was to use get all the reg setting the way I want, export them, get them into a .rgu file and then build them in. Any ideas?
How do I get it so that ini_tray.lnk is not automatically in startup?.
Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?
dcdivenut said:
Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?
Click to expand...
Click to collapse
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)
mfrazzz said:
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)
Click to expand...
Click to collapse
Cool, will check when I get home, any thought on post above?
Hmmmmmm...
Seems to me your mind was on your woman and not your Wizard... just a thought,ehehe!
Congrats bro!
My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...
Madcap180 said:
My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...
Click to expand...
Click to collapse
dc just got engaged.....
Congrats DC ... if you ever need someone to pick the lock on that ball and chain, let me know...j/k
Sorry if this is another noobish question, but since I've been experimenting with cooking in the CORE Kitchen lately, I was wondering, are the files in the SYS and OEM parts of the kitchen interchangeable? I've been recently trying to use the ingenetic's rom to install the basic options that I would like (I don't use bt, so most of those features aren't needed), and noticed that some information appears to be in the SYS folder by default when dumping the rom.
an example would be something like the comm manager, which appears to already have some files in the SYS folder, but there was an htc option to click off on build os, since i think the oem package had it listed (part of the oem package download in the same thread as the kitchen). also the files for office appear to be pre-existing in the sys folder, so was wondering if the build os checkbox meant anything...
I've tried cooking roms with the options checked off and on and haven't noticed any differences, because the roms usually ended up being built and flashable, but the roms always came out screwed up. (office shortcuts would not appear, although they could be run from the \windows directory or an option to put the date information on 1 line didn't work).
I'll probably try to figure out how to use faria's kitchen and try to make the same mods, since it looks like the cookers themselves seem to have been using that kitchen for their original builds...
One thing you will find out is all the kitchens (at the lowest levels) are basically the same since they all use the same set of tools. Where the differences come is just layouts (and even then, they are still all pretty close. Core Kitchen is probably the one that is the most different, and thats just because its been laid out very logically (and not just hacked together IMO) and scripts and shortcuts setup to make it all look and feel like a nice organized set of tools. I've been using Core Kitchen mainly since Crossbow Reloaded 1.7 and I really like the layout and all. But definetly try other kitchens so you can see how they all came from the same roots (and you start to realize how this all fits together).
As for OEM and SYS... Well SYS is supposed to be what the base rom is. And OEM is the add on packages. But different cookers do things differently. I'll admit that I get sloppy sometimes and will drag stuff out of SYS and into OEM if I'm completely changing it, or sometime I edit stuff directly in SYS and maybe make rgu or initflashfile stuff for it over in OEM (so yeah, anyone dumping my roms may find some odd things in odd places. Sorry, it makes sense for me at the time I worked on it, and some of it is tricks / techniques that I've seen in Faria's stuff).
So yeah, I guess you could say OEM and SYS are interchangable. In my ROM Windows LIve stuff is in OEM since it was brought from elsewhere (but then Office was brought from elsewhere but I left it in SYS as I had issues when I tried to move it).
Good luck!
lol...coincidentally the base roms i was using look like they were from you...both your tweaked version of the base wm6 from ingenetics and xm6. maybe that's what causing all these error messages to popup when i try to buildos. says it already has files here and there.
if you have experience with core kitchen, would you know if i can still flash the file that is created, even if the error message pops up? the error that i usually get in buildos is that the file already exist elsewhere (though i need to play with a bit more to figure why, since i can't find the file in more than one location when i do a search). not sure if buildos finishes its build or it just stops (the included tutorial says to try to fix the error and not continue flashing...but just curious).
anyway, it looks like there was another version of the base ingenetics rom in the forum posting, so I'm gonna try tossing that into the core kitchen to see if i get the same errors in trying to cook it.
thx for the comments.
First of all, i want to say thanks mfrazzz for the nice words...i apreciate it !
Second ...if it gives you any error then the product is corrupted, that is very easy to understand...Because when Build OS encountered an error it stopped and won't go trough with the whole process. So if any errors, abort and check the log and fix what can be fixed.
monkey_knight said:
lol...coincidentally the base roms i was using look like they were from you...both your tweaked version of the base wm6 from ingenetics and xm6. maybe that's what causing all these error messages to popup when i try to buildos. says it already has files here and there.
Click to expand...
Click to collapse
Yeah, if it says that the file is already there, then you have to stop and find out where the duplicates are. Most likely there are files in OEM and in SYS with the same name. You then have to figure out which you want and remove the other (or rename it and then in initflashfile.txt change the name back to what you want when you move it to a different directory).
But if you get errors, (duplicate files, hive not created) or the like, you have to stop! You can't move on as things didn't complete.
If you want a clean version, then use the Ingenetics base and the packages that matt put together. Thats all made to work together. If you start with my base, then you have to keep moving forward from there, and I threw XM6 and the first version of Ingenetics together in a matter of hours so they are not laid out very well. Part of what I want to do with this next XM6 is take my time and do this one right (but I was trying to get that base out to the masses and get a better working Crossbow Reloaded 1.7 type rom on it, and wasn't thinking of people using it to start their own cooking with either of them ).
Okay. I have exhausted all possibilities that I can think of for this problem. The last few ROM's I've ported have been fine, except for one thing. After flashing (or hard reset) the ROM displays the splash screen and then goes to the welcome screen (displays welcomehead.96). However, when the LogoMsg.bmp popups up (the text that says, "The device is clearing the storage. Please wait.) it only displays for a few seconds then leaves. A few seconds later the tone that accompanies the "Tap screen to begin setting up your device" sounds. The words, "Tap screen..." do not show. However, a second or two later the tone sounds again, this time followed by the text, "Tap screen to begin...". From here everything in the ROM works fine. I just cannot figure that part out.
The LogoMsg.bmp is located in OEMDrivers, so I thought I might have accidentally removed something from the OEM folder. However, I have not found anything seemingly related. Also, I thought it might have been related to welcome.exe. Though, I've tried replacing it with an older version; still no luck. Unfortunately, I have tried so many things that I cannot remember exactly what all I have tried. I've re-ported XIP's (using Ervius' kitchen and by hand) and SYS's, as well as taking a fresh copy of my base OEM.
Essentially, I am asking if anyone has come across anything like this in your cooking, and if you have any tips. I would be more than happy to upload a copy of my ROM for you to test or upload my kitchen folders. I appreciate any help that anyone can provide.
EDIT: I'll try and upload a video later to show exactly what is happening.
Hi KMFM$
I use an official rom iolite ita for porting the xip e Sys to my kaiser. After cooking i have the same problem that you describe.
After 2 mounth there is some solution... i'm crazy for this problem
Bye
Daniele
i have the same issue when flashing any of the wm 6.5 ROM's. not sure what kitchen the chefs use but it doesnt seem to effect anything.
Well, I have yet to find a "solution" to this. However, I have just simply learn to deal with it. It does not effect the ROM in any noticeable way, and from what I've heard from other chef's, this is common in all new ROMs. Not sure what is going on in the ROM during that time frame, but again, it does not effect the standard operation of the ROM.
well dont sweat it then. yeah, i think its normal for 6.5
yep been a normal thing for all my 6.5's
hi KMFM$
the ROM is 6.1 or 6.5?
When it comes to porting it depends on build ver. ect ect. Its a big try and fail operation for moust of us when thing doesnt work as planned. But to get a true port you have to use m'relloc and manual change values in the modules, there is alot of guides on how to.
On dump of nbh in kitchen it unpacks diffrently (provider to provider or if its a "pure" HTC nbh), anyway the cue is that some of the chef`s use xip files in the ROM folder while other make mxipkernel + mxipkernelLTK in SYS and oemxipkernel in OEM then os.nb+ a folder named XIP in ROM and THAT contains boot.rgu I use the last method which for some reason works best for me.
- shifu - said:
hi KMFM$
the ROM is 6.1 or 6.5?
Click to expand...
Click to collapse
Both, actually. WM6.1 builds from about CE OS 5.2.20757+, I believe, have all given the "extra" notifier. Again, I'm over it. I've just accepted the extra tone and moved on. No big deal.