Database Users

[FYI] Things to know when use TMOUS_HD2_2.13 as Base

Is it save to cook a TMOUS 2.13 stock rom for a HD2 WWE??? I would like to use the 2.13 as base... are there things i have to look out for? Here r some tips i got from some helpful people..
millski said:
There's no connectiondb oem or connectionsetup/connectionsetup_wvga packages ext in the 2.13 stock rom, you'll probably want to get those from somewhere else (so that connections are correctly set for other networks on first boot). Also the TMOUS 2.13 operatorpkg is full of TMO theme stuff (boot screen, WM 6.5 tsk, TMO app icons etc). I replaced my operatorpkg with an HTC stock pkg...
Click to expand...
Click to collapse
see attachment.... Load Connectionsetup to EXT and Connectionsetup to OEM... I also copied the lines u find in the app.reg file, paste it in initflashfiles.dat... for sure. i believe that connection setup will be loaded on startup this way, correct me if i'm wrong...
NIKOSXRI said:
.......All externals work fine, but if the touch feeling is not good for you, then just replace the touch.dll and touchgl.dll from stock rom.Then touch is much better and soft.
Click to expand...
Click to collapse
got these attached too..
Look into \OperatorPkg\mxipupdate_oemoperato rs_102.provxml
this provxml sets all 9 quicklinks that comes with TMoUS. You might edit them to set your personal quicklinks right after flash... Thanks tidus18
Thanks for these tips... Tested and working tips r always welcome ofcourse

it is save! nothing to look for

Edited to clarify things...
Solved

Thanx!!.........

There's no connectiondb oem or connectionsetup/connectionsetup_wvga packages ext in the 2.13 stock rom, you'll probably want to get those from somewhere else (so that connections are correctly set for other networks on first boot). Also the TMOUS 2.13 operatorpkg is full of TMO theme stuff (boot screen, WM 6.5 tsk, TMO app icons etc). I replaced my operatorpkg with an HTC stock pkg...

millski said:
There's no connectiondb oem or connectionsetup/connectionsetup_wvga packages ext in the 2.13 stock rom, you'll probably want to get those from somewhere else (so that connections are correctly set for other networks on first boot). Also the TMOUS 2.13 operatorpkg is full of TMO theme stuff (boot screen, WM 6.5 tsk, TMO app icons etc). I replaced my operatorpkg with an HTC stock pkg...
Click to expand...
Click to collapse
Yeah found out after flashing my own rom.... working on it now!

millski said:
There's no connectiondb oem or connectionsetup/connectionsetup_wvga packages ext in the 2.13 stock rom, you'll probably want to get those from somewhere else (so that connections are correctly set for other networks on first boot). Also the TMOUS 2.13 operatorpkg is full of TMO theme stuff (boot screen, WM 6.5 tsk, TMO app icons etc). I replaced my operatorpkg with an HTC stock pkg...
Click to expand...
Click to collapse
You should take the one from stock rom and also you must do changes in the operator package oem, of course, if you dont live in the USA.
You may also have to replace the tmous phcanoverbmp dll in this oem package.I dont know if this dll works because i use my custom dll.
All externals work fine, but if the touch feeling is not good for you, then just replace the touch.dll and touchgl.dll from stock rom.Then touch is much better and soft.

NIKOSXRI said:
You should take the one from stock rom and also you must do changes in the operator package oem, of course, if you dont live in the USA.
You may also have to replace the tmous phcanoverbmp dll in this oem package.I dont know if this dll works because i use my custom dll.
All externals work fine, but if the touch feeling is not good for you, then just replace the touch.dll and touchgl.dll from stock rom.Then touch is much better and soft.
Click to expand...
Click to collapse
Ahaaa... I thought so that the touch was different... It was freakin me out!! I had better on other ROM's indeed. Thanx for the great tip man...
+ Que PPC... Changed the title of this thread... hope u don't mind...

No prob for me... but you need to change it again man... why? cause you are talking of some other things now... keep it up

NIKOSXRI said:
You should take the one from stock rom and also you must do changes in the operator package oem, of course, if you dont live in the USA.
You may also have to replace the tmous phcanoverbmp dll in this oem package.I dont know if this dll works because i use my custom dll.
All externals work fine, but if the touch feeling is not good for you, then just replace the touch.dll and touchgl.dll from stock rom.Then touch is much better and soft.
Click to expand...
Click to collapse
Very good tip indeed...i feel the touch in this rom is not as good as the stock rom. i was thinking of using some older based as i thought i screwed up something in this base.
Thanks NIKOSXRI!
P/s: As +Que PPC said, i propose to change topic to tip/things to look out for when cooking with Base 2.13.

Hopefully this title means a general topic jiji
Mod edited to change the title.... again

tidus18 said:
Very good tip indeed...i feel the touch in this rom is not as good as the stock rom. i was thinking of using some older based as i thought i screwed up something in this base.
Thanks NIKOSXRI!
P/s: As +Que PPC said, i propose to change topic to tip/things to look out for when cooking with Base 2.13.
Click to expand...
Click to collapse
Also i noticed that touch response (I mean the software), if you use it, though is very helpfull and i like it, changes the responsiveness (sometimes you tap a button with no response) because it uses its own driver.
If anyone uses it i want to hear his comments on this.

any one knows where to find the reg file to modify those tmous quicklinks... found they where in HKLM\Software\HTC\Manila\Home, but in which EXT pack (app.reg) lies these reg keys???? tried to look in OperatorPkg, but no go...

kurniawan77 said:
any one knows where to find the reg file to modify those tmous quicklinks... found they where in HKLM\Software\HTC\Manila\Home, but in which EXT pack (app.reg) lies these reg keys???? tried to look in OperatorPkg, but no go...
Click to expand...
Click to collapse
Hope this is what you mean:
EVK\OEM\LEO\0409\OperatorPkg\mxipupdate_oemoperators_102.provxml
Click to expand...
Click to collapse
this provxml sets all 9 quicklinks

Exactly what needs to be changed in kitchen to avoid robo voice

I used wavedev.dll and rilphone.dll from birkoff's (chuckydroidrom) kitchen, as modules. I'm an EVK guy and I use rstoyguy's kitchen to cook my own rom for my hd2. The only info I could find was about changing those two.. It seems birkoff used 2.10.1 as a base.. Including the 2.13 gps drivers as an ext. Is there anything more specific? I'll try to figure out.. then hopefully I can add a nice [ref] tag to this post. heh

Just tried the ChuckyDroidROM OEMDrivers folder.. Only the modules.. no luck. Its annoying because one 'robocall' is all it takes to break android sound... not to mention all the rom flashing i've done. Any help guys?

1. Hspl
2. Radio 2.12 or 2.10
3. Miri elegancia or chuckydroid
4. Your android version
Did u try any of those combos?
Make sure u have one of those radios. There pretty important.

Yes, I've got that part down. I've tried every radio, and I've confirmed that chuckydroidrom does solve the voice issues. I'm asking what birkoff changed in the kitchen to get chuckydroidrom to work without issues with android. I could port all my stuff over to osKitchen, including sys (I use com2 builds) - but then i'd never really know for sure.
to recap, so far i've got oemdrivers (modules only), rilphone and wavedev (which are part of oemdrivers) from chuckydroidrom.. but that hasn't cured anything. It seems like OEMDriversHigh is identical to the set I have. Other than that, theres the sys build (I have 21915) and the many different exts. I build com2 21915 with 2016 sense and 1.8.5.1 CHT.. The rom is like 190MB tops.
So is something missing.. or is something that I'm including breaking functionality? I'd like to find out here rather than the long trial and error process ahead of me.

Ok, so I was able to actually break sound in winmo by using the OEMDrivers from birkoffs kitchen. I got the robo voice and all that, the whole nine, so to speak. I wonder if this is relevant. There are probably two things that need to match up in winmo that didn't- most of the time, one of these things don't match up in android, causing robo voice. What carries over to android that is not in OEMDrivers. Rilphone and wavedev alone broke nothing in winmo, but retained robo voice in android.

You need to use CAD.dll, dsm.dll, oncrpc.dll, remote_apis_clnt.dll, wavedev.dll, audio_cal.acdb from a 2.10 OEM to get rid of robo voice.

pkoper said:
You need to use CAD.dll, dsm.dll, oncrpc.dll, remote_apis_clnt.dll, wavedev.dll, audio_cal.acdb from a 2.10 OEM to get rid of robo voice.
Click to expand...
Click to collapse
You are the ****ing man.

I changed rom and I got rid of robot voice

My HD2 Kitchen is available here if you want also. it has a saved project to cook a rom android compatible

Thanks for the link to the kitchen, thats a big one! Well, the aforementioned files did not fix incall robo voice but managed to lock up phone when volume was adjusted in winmo.
What sys does the kitchen use for the droid rom? I'm not trying to build a barebones rom - I'm just trying to adjust my build for in-call sound to work in android.

Ok.. so 21911 is the sys..
I included the 2.10 OEMDrivers and OEMDriversHigh - that still did not work.
On the boot screen, it still says 2.13 for "D" - where R would be radio version. With those drivers, winmo also seemed a great bit choppier. Its back to the drawing board for me..

joshkoss said:
My HD2 Kitchen is available here if you want also. it has a saved project to cook a rom android compatible
Click to expand...
Click to collapse
Was able to get your kitchen set up with a couple of my exts, manila folder (a couple tabs removed), cht, and 21915. I flashed the rom, the "D" read 2.10Droid as expected.. and somehow someway I still get the robo voice. I tried 2.08 radio, 2.12, and 2.10. Same thing.
Now I'm confused.. Could it be something like an updated version of audio manager, audio booster, anything like that? Probably not, as there are roms that work with android that have cht, latest version of manila and so on.
I'll try a few more things..
edit: audio seemes to be really screwed. Any sound played in winmo, locks up my phone. This is crazy. What am i screwing up?

Sounds like your kitchen is all over the show.
Make sure you work with clean sources. I have several untouched stock rom dumps to have quick access to original files.
The files posted earlier definately get rid of robo voice. I also took OEMXipkernel from 2.10, but not sure if this is necessary.
Have you flashed the stock 2.10 ?

pkoper said:
Sounds like your kitchen is all over the show.
Make sure you work with clean sources. I have several untouched stock rom dumps to have quick access to original files.
The files posted earlier definately get rid of robo voice. I also took OEMXipkernel from 2.10, but not sure if this is necessary.
Have you flashed the stock 2.10 ?
Click to expand...
Click to collapse
This was from a clean source.. or rather.. one that is proven to work. The only major changes I did was updating the manila/htc related packages. Would it matter if I had the aforementioned files as modules instead? Good tip on the 2.10 oemxipkernel. I wonder if that is in kitchens like birkoffs and josh's.

Bump. According to the troubleshooting thread, there is still very little info about this.
Any tips or guesses? I'll start cooking whatever tonight.

I think this is the path to the answer. Each android build performs flawlessly with stock ROMs. No freezing or non working hardware. Everything works (for me on TMOUS anyway). I am not looking for a solution to robot voice, I am stating that from my point of view when booting any android build from a stock ROM on my TMOUS HD2, every thing works fine except for the robot voice. Bluetooth,good, Wifi,good, no freezes or SOD. Smooth as a babies butt! I personaly believe that crossing this barrier will mark the start of something great for our developer friends.
Sent from my HTC Desire using XDA App

Well, as I might have stated before, I was able to reproduce robot voice in winmo by frankensteining 2.13 and 2.10 together. In winmo, anytime a sound would be played.. it'd lock up. Its not really a developer issue. Its more like a mismatch of versions. The android sound driver could do things the same way as 2.10 sound driver.. I'm being sorta vague.. but its a very strange problem.. Especially when you introduce radio version into the mix.
How could something happen like that? What has to go wrong? Is it the way the hardware is initialized? or is it the way its accessed?

Did you try a clean 2.10.1 base without mixing any drivers...and I mean CLEAN
OEMXIP also from it including nk etc....

[29OCT] osKitchen GhostXSeries EURO&TMOUS Cook your own ROM for all chiefs Ver 9.5.0

[29OCT] osKitchen GhostXSeries EURO&TMOUS Cook your own ROM for all chiefs Ver 9.5.0
Why settle for other peoples roms! Can you find one that is exactly the way you want it? Download my osKitchen and build your own rom from scratch with the packages and look you want!
My kitchen is easy to use and is built on stock look so you can customise it the way you want to!
I am more than happy for you to build roms from it and even upload to XDA. If you do all I ask is that you mention me in your thread for using my kitchen. If you download my builds, I do not accept donations but please press the thanks button!
29th October 2011 - Version 9.5.0
Full download Here: - Mirror provided by poyensa
poyensa's Build Full download Here:
Patchs & updatespost #2
Useful Hints and Tips in post #3
Click to expand...
Click to collapse
Video demonstration of osKitchen build ver 6.5
Some Roms that have been built using my Kitchen build!
GuzuGuzu 6.5.5 ROM with CHT 2.0 thread here:
poyensa 6.5.5 ROM with CHT 2.0 thread here:
ShiftPDA 6.5.5 ROM thread here:
Kefir.net 6.1 ROM thread here: - The first WM6.1 ROM for the HD2!
NinoFR a French trasnlation of my osKitchen - Download here:
Click to expand...
Click to collapse
The details of the kitchen are as follows:
Kitchen Details WWE
RAM: 576
OSKitchen Zero: 1.33.5
Base Image: Tweaked RUU_Leo_1_5_TMOUS_3.14.531.0 completly new base!
OS: 21913 and 23193 - NEW! - Both OS tweaked by me!
Sense: 2018 & 2021
XDA_UC Compatable!
Office 2010
Facebook 1.1.0.26
Cookie Home Tab 2.0
Opera version 10
PPCPimBackup
Click to expand...
Click to collapse
Change Log
Version 9.5.0
Sense 2021 - Some minor tweaks
Fixed all leds so now they flash untill you go in and clear the alert! Not even availble on standard roms!
Fixed Internet Sharing (Hopefully!)
Some other minor tweaks
Click to expand...
Click to collapse
Beta Testing team!
GhostXSeries
GuzuGuzu
poyensa
ShiftPDA
Click to expand...
Click to collapse
Disclaimer
I will try to help you out with issues if I can, but I will not take any responsibility for faults with your device!

This will be reserved for minor updates to the kithcen - This means you will be able to download the updates directly instead of having to donwnload the full kitchen each time.
9.0.0 11/10/2011 updates
View attachment 746595 Wifi router sharing
9.0.0 12/10/2011 updates
View attachment Backlight.zip Enable backlight
Tools:
View attachment LeoAdvancedRUU.zip Leo Advanced Updated utility. Thread here: All credit goes to Barin for creating the app and to HD2Owner for the thread!

Useful notes:
How to add a cab file as a package in your build!
First make sure you have the files you need with a .cab extension. This is the easiest way to do this. Drop the files into a location eg desktop.
.Open osKitchen go to Import
.Select button for cab installer file
.Press Browse and select the .cab file from the desktop
.Under Device Drop down select HTC Leo
.Uder Group select an existing group eg 04 Software, or if you want to create your own group type in the name here
.Under Name type in what you want to call Ext package
.Press Convert
You will then see a window with Operation completed press Ok
Close the windows and go into Ext packages and select the newly installed package!

Change Logs
Version 9.0.0
Sense 2021 - Fixed Sense restart issue now works with 3rd part apps
Changed multiple reg keys to make sense more stable
Fixed IE colour issue with os 23153
Added option to hide or show the operator text in the top curtian
Able to edit the top bar and bottom bar to match wallpaper
Some other minor tweaks
Version 8.5.0
New OS 6.5.3 23153
Fixed bottom buttons on 6.5.3
Added SDKCert
Some other minor tweaks
Ultrashot driver fix for bold font replaces gwes.exe
Version 8.0.0
New kitchen built from scratch!
New base used. I have now used base rom RUU_Leo_1_5_TMOUS_3.14.531.0 rather than trying to merge different bases together.
FM Radio fixed!
Weather animations on home screen Fixed!
Sense 2021, now you can see the operator carrier at the top of the screen.
Version 7.5.0
Sense 2021
Fixed restarting issues with third party apps thanks to Poyensa
Tweaks
Fixed security policy now you can install HTC hotfixes!!
Other minor fixes
Also please test in the people tab: all people-update & events tab - seems to be stable for me, but please test!
Trimed.......

Wonderful, thank you so much for this release. I'll get cracking on adding the things i wanted to this build and let you know how i get along. Do you want a copy of the updated Copilot cab to add to your builds?

Just in case

@GhostXSeries : Sent you PM on robotic voice.
Btw why are you on such old build for WM 6.5 ?

I wanted to give the option of upgrading the orgional builds so chiefs can have a choice. It was purely an exercise for me to see if it could be upgraded to the 576mb with office 2010 and .net etc.
I also had the phone on stand by with hspda last night and if my battery is right it dropped about 4 percent!!!!!!!

576mb android compatable kitchen now available for download

Thank you very much but now I still cant test your ROM Your link is very slow (
Please upload on megaupload.com, hotfile.com, mediafire.com, multiupload.com,...
Thanks

Sorry I am only going to be storing the images on VBN from now on. It is too much work to upload to multiple sites.

Downloading the Android compatible rom now, looking forward to finally having a nice, close to stock Rom that works smooth.
Keep up the great work.

gaiden0000 said:
Downloading the Android compatible rom now, looking forward to finally having a nice, close to stock Rom that works smooth.
Keep up the great work.
Click to expand...
Click to collapse
I am currently working on a sense 2018 version that is also Android compatable. This will be up in the next couple of days. I have got sense working on the build I am just simply trying to modify the base build to tweak it a bit. I will hopefully have a mixture of tmobile 2.10, 2.14 and leo 1.66

Kitchen build has now got Sense 2018! As far as I can tell this is the first Kitchen to be released with Sense 2018 included

Hmm.. tried your kitchen, but (knowing not much about kitchens...) tried to find a project file (.kxml file) to load, but can't find it.
Can it be you missed that one? Or do I have to set up my own?
(e.g. an example ROM would be great)
One question: When the ROM is very small (eg. removed Windows Live and Office) will the memory for data storage be any larger?
one more.. Some imageinfo.bin files are read only. This gives an error when building (because the file cannot be overwritten) Is this ok or an error?

Bright.Light said:
Hmm.. tried your kitchen, but (knowing not much about kitchens...) tried to find a project file (.kxml file) to load, but can't find it.
Can it be you missed that one? Or do I have to set up my own?
(e.g. an example ROM would be great)
One question: When the ROM is very small (eg. removed Windows Live and Office) will the memory for data storage be any larger?
one more.. Some imageinfo.bin files are read only. This gives an error when building (because the file cannot be overwritten) Is this ok or an error?
Click to expand...
Click to collapse
It is very easy to built your own project files. Simply select the operating system on the first screen eg os 21869 (WM 6.5) or 23569 (WM 6.5.5) then when you go into the ext packages screen simply select the packages for the operating system eg:
If you select 21869 then select
01 HTC Packages - This is the list of the main packages
02 Sense 2018 fixes if you want to remove the rss feader,
03 23569 fixes - Do not select this - only use this for OS 23569
04 Tweaks - You can select what you want from this
05 Software - You can add what you want into this folder extra programs etc
If you select the 23569 OS remember to go into Sys Packages and select everything for beginers, and select 03 23569 fixes. This folder updates things like the dial pad and the keyboard etc.
I simply tried to keep the Kitchen rar file as small as possible!

For the read only error, simply right click on the osKitchen folder, go to properties and uncheck an read only check boxes! Sorry about that I kinda forgot the check the permissions on the folder before I uploaded it

GhostXSeries said:
For the read only error, simply right click on the osKitchen folder, go to properties and uncheck an read only check boxes! Sorry about that I kinda forgot the check the permissions on the folder before I uploaded it
Click to expand...
Click to collapse
Already did - thanks.
I want to remove Sense altogether, also I don't use Office (using a better office suite)
Is it also UC capable? (And, could you please answer my question about the memory gain when the ROM has less packages in it?)

Bright.Light said:
Already did - thanks.
I want to remove Sense altogether, also I don't use Office (using a better office suite)
Is it also UC capable? (And, could you please answer my question about the memory gain when the ROM has less packages in it?)
Click to expand...
Click to collapse
Memory will be better the less packages you remove. If you dont want sense, you can simply de-select all the manila packages and the start icon loader package as well. It is not currently UC compatable, I have not done much work with this yet, but you should be able to download the cab files and add them in to the package.
What other versions of office are you using?

Just wanted to write back to say that I've been cooking away using your kitchen build and it's got to be one of the best one's I've used. I'm so close to perfecting my own Rom and it's all thanks to you.
Have you tried including the Chainfire 3D drivers? When I've tried it's not gone right (this isn't a problem with your kitchen, as i think it's an issue with OSkitchen and the 3D drivers from what i've been reading). Thanks again for this.

[SOLVED] Non-booting ROM - I'm doing it wrong

Greetings!
First off, I have little idea what I'm doing, this is my first attempt to create a custom ROM. I've searched around and can't seem to find a solution.
I've got an Xperia X1 and am using osKitchen.
The ultimate goal is to have a Japanese ROM with WM build 25369 with no additional UIs, i never use sense or whatever anyway, just the old today screen with cal, messaging, and time/date items.
I have:
Latest stock ROM for X1 (GENERIC_NAM_R3AA011)
23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 (Just Eng)
initflashfiles-dat-all-langs-updated-feb-24-2010.zip
RUU_Diamond_eMobile_JPN_1.81.881.2_Radio_Signed_Diamond_52.48.25.26_1.09.25.07_Ship.exe (6.1 JPN ROM)
Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip
WM6550-23563-Rollup-All-Pkgs.rar (This has all languages)
Here's what I'm doing, anyone of them (or all) could be very wrong, hopefully I've done at least one thing right:
Imported X1 ROM for OEMDrivers, OEMApps, OEMOperators, oemversion, oem_dpi
Imported 6.1 JPN ROM for OEM Lang 411
-What i did here is i copied everything over from the JPN rom's oem 411 folder into the X1 OEM Lang folder, overwrote any conflicts, deleted any 0409 muis, and copied over the file from initflashfiles zip for 0411.
Replaced OEMXipKernel with the one from Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip and selected custom XIP when making the rom with the one also found in that zip. Put the rest of the files (os.nb.payload, xip.bin, uldr.nb0, romhdr.bin) into the ROM Parts folder.
Then, I Used OS, OSFiles, MSXIPKernel, MSXIPKernelLTK from the 23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 zip, and the rest of the packages i used from the WM6550-23563-Rollup-All-Pkgs rar (because it had 0411 files).
I deleted dpi and lang folders that my device doesn't use (it uses 192dpi 480x800 and 0411) and built the ROM, flashed, and it shows the Sony Ericsson splash screen, and then goes black forever.
I know I must be doing something very wrong, any hints as to what?
Thanks

Pfff, what a big list,
Okay I did it this way, and I make my rom in 12 languages and they are all working.
1. Install oskitchen and import xperia rom
2. After finishing import 23563 build
3. Install another oskitchen and import diamond jpn rom
4. Copy the oem_lang 0411 and the ext packages to your kovsky kitchen be aware you put them in the right place.
5. Open the kovsky kitchen and select the Japanese language and select the packages you wanna use in your rom and you're done.
Regards,

Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?

nemasu said:
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
Click to expand...
Click to collapse
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,

Rataplan said:
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Click to expand...
Click to collapse
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?

nemasu said:
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
Click to expand...
Click to collapse
If you extract the 23569 build, you only have to change the All and Common folder, but in your first post you where talking about a 25369 build and I didn't know what kind off build that was.
Succes buddy,

Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.

Farmer Ted said:
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Click to expand...
Click to collapse
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.

nemasu said:
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
Click to expand...
Click to collapse
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.

Rataplan said:
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Click to expand...
Click to collapse
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?

nemasu said:
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
Click to expand...
Click to collapse
No I have them also, never take a look at it, only checked the file when I cooked my rom's never changed anything or replaced it with another version or from another build.

[Q] Problem with Phone Canvas Enhancement 2G v4.0.52619223128.0 in com2 build.

Problem with Phone Canvas Enhancement 2G v4.0.52619223128.0 in com2 build.
Hi all, just have an issue and I can't point the finger on the right place to get this one solved
So I'm asking for some help, I'm using the Phone Canvas Enhancement mentioned above, and it works perfect on a com3 build but
for some reason when I cooked this one in a com2 build the options for the dialer are not working.
I'm using the same kitchen, for com3 and com2 with the same pkg's and everything is working the way it should work.
Only in the com2 build I'm not able to setup the call-specific options.
Already changed the mui files, used another dummy_sqm but still no difference.
The com2 build I'm using is 21916, also tried 21914 but no difference.
Someone else have any idea ?
Thanks,

Ok, just want to give it one more try so BUMP

Hi,
Did you dump the rom yourself or are you using predumped packages?
Phonecanvas in com 3 needs some fixes like the softkeypad.
Also did you look in operatorpkg?
Have a look there which phcanOverbmp.
Is it HTC or T-Mous?
That's all I can think of.

Laurentius26 said:
Hi,
Did you dump the rom yourself or are you using predumped packages?
Phonecanvas in com 3 needs some fixes like the softkeypad.
Also did you look in operatorpkg?
Have a look there which phcanOverbmp.
Is it HTC or T-Mous?
That's all I can think of.
Click to expand...
Click to collapse
I dumped the rom myself, import the 23569 build and import the 21916 build, made a small change on the 21916 build (changed office mobile to office mobile 2010) and edit the file phcanrc, build rom in 23569 no problem, and in 21916 issue with the options.
There is not much left in my operatorpkg only the animated.gif and the Mega_phcanOverbmp, so I have to see if that causes the issue, but I still think it's strange that I don't have it with the 23569 build.
For now really thanks for the info, I'm gonna work on it and keep you informed if this will solve it.
Btw nice site you have
Greetz,

Try to use the phonecanvas as it's (if possible) and use the correspondending phcan in operatorpkg.
Another thing you need to check is the reg in operatorpkg, if it directs to the phcan you are using.
In my case:
[HKEY_LOCAL_MACHINE\Security\ResOver\Bitmaps]
"Basedll"="leo_phcanOverbmp.dll"
"BaseId"=dword:00000000
"BatteryIconIdStart"=dword:000003E9
"BatteryIconLevels"=dword:00000015
Click to expand...
Click to collapse
Thanks for the compliment about the site.
Rataplan said:
and edit the file phcanrc, build rom in 23569 no problem, and in 21916 issue with the options.
There is not much left in my operatorpkg only the animated.gif and the Mega_phcanOverbmp, so I have to see if that causes the issue, but I still think it's strange that I don't have it with the 23569 build.
Greetz,
Click to expand...
Click to collapse

What do you mean with "call specific options"?

pkoper said:
What do you mean with "call specific options"?
Click to expand...
Click to collapse
I mean the advanced options, sounds, network, gsm/umts, headset it's a submenu from the dialer, I think that Laurentius26 is right because I miss the registry key for phcan, I'm gonna check it this evening.
Still wondering why I don't have a problem with a com3 build.
Keep you all informed

Somewhere in sys, maybe Phone or Phoneredist I can't remember, it is set to not display.
Check your reg for
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
remove
redirect=""
if its there.

pkoper said:
Somewhere in sys, maybe Phone or Phoneredist I can't remember, it is set to not display.
Check your reg for
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
remove
redirect=""
if its there.
Click to expand...
Click to collapse
Okay thanks gonna try that, because changing the reg. made my kitchen crash.
Greetz,

Ok, I give up, I build 12 roms with 21916 (all different languages) until I noticed the issue, went back to 21914, same issue.
Tried what you both suggested, kitchen start crashing, went back to the original 21854 with the same pkg everything working normal also the options menu in the dialer.
So the problem must be in the changing the office pkg or a kitchen-update because thats are the only things I've changed.
And I'm not even sure about the kitchen-update.
For now I'm not sure what I've changed to give an honest answer if I get this solved.
Just want to say thanks the both of you, together is power
Regards,

I went through some unmodified builds.
The reg key is in the rgu in SYS\Phone....
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"Redirect"=-
Sorry, made a mistake in the previous post

pkoper said:
I went through some unmodified builds.
The reg key is in the rgu in SYS\Phone....
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"Redirect"=-
Sorry, made a mistake in the previous post
Click to expand...
Click to collapse
Yes, I know, I already found that reg key, but for some reason my kitchen keeps on crashing when I use the 21916 build, so I can not tell you if the trick you told me is working.
In short what I tried:
1. Edit the reg key for the phcan.
2. Deleting the reg key in the Phone pkg.
3. Changing the Phone pkg and use the one from 21854.
4. Building without ext-pkg
5. Make a switch to 21914 and repeated the 4 steps mentioned above.
But for now the kitchen keeps on crashing when I'm using the 21914 or 21916 build, which is very strange because I cooked several roms with it also cooked without the office pkg but still no change.
For now I'm gonna download another com2 build and see if that will do the trick.
In Dutch: Schiet mij maar lek.
In English: Shoot me.
And again really thanks for trying to help me.
Greetz,

Sorry forget my post.

Ok downloading and importing the 21916 again did the trick, download the build from mobileunderground, normally I used the builds from ppckitchen not sure if they are different.
The only thing I can think about for now is that when I'm upgrading my kitchen, went from 1.25 to 133.3 (oskitchen) always in small steps but the only thing I changed was the exe file and the resource folder, and maybe there it went wrong.
I know it is not a real solution but for me this one is solved.
Thanks,