Related
How do you uninstall a CAB file that is just a modification, but not a program, so it doesnt show up in the remove programs list...?
Specifically this one...
"battery_ou_081304.sa.cab"
I dont like how no matter what themse you have, it uses a blue background on the battery meter, so it conflicts with the default blue theme, which I like, but is darker, so the battery in the corner looks bad.
-connor
oh i figured it out....(for anyone else who searched and found this thread)
run same CAB file again, it will say it has to uninstall before it reinstalls, then it will ask where to install again, and you can just cancel at that point so it doesnt add it back.
cool - thanks me, lol.
-connor
Thanks for this info, I was looking for this.
Hi guys,
I wanted to give cooking a try and was wondering what the easiest approach for me would be.
My goal is to use the official ROM as a basis and
a) remove an app such as CoPilot
b) add an app such as Pigeon
What tools etc. would I need?
Thanks for any hints
remove/add prgs is no ROM-cooking, it´s removing and adding apps .........
So then tell me, how can I remove CoPilot?
Anyway, the two points were starters...
I'm sure I will do more modifications later on.
Search for 'kitchen' and you'll get more info on it
pub00515 said:
So then tell me, how can I remove CoPilot?
Anyway, the two points were starters...
I'm sure I will do more modifications later on.
Click to expand...
Click to collapse
Move Copilot-prog to SD-card with Resco-Expl. and then uninstall it, Afterwards make a reg clean-up with reg cleaner (a little bit crude though but worked nicely for me )
troed said:
Move Copilot-prog to SD-card with Resco-Expl. and then uninstall it, Afterwards make a reg clean-up with reg cleaner (a little bit crude though but worked nicely for me )
Click to expand...
Click to collapse
If you do that there are still files in the ROM you can't get rid of. Plus a duplicate of what you just deleted, don't forget the files that are in Program files after a hard reset must come from somewhere
Complete removal can only be done by cooking, and it saves quite a bit of space indeed.
I'm wondering if various included applications such as the Bing widget, Blockbuster Mobile, B&N eReader, the Gameloft game demos, and so on... could be removed? SAFELY, of course.
They just create what seems to be (and probably is) unnecessary system bulk. Not to mention, those game demos are completely hideous, and they obscure the potentially "uncluttered" Start Menu applications tray that could be had.
Could someone perhaps offer a bit of insight, maybe even enlighten me a little bit on this topic? Thanks.
Reignzone said:
I'm wondering if various included applications such as the Bing widget, Blockbuster Mobile, B&N eReader, the Gameloft game demos, and so on... could be removed? SAFELY, of course.
They just create what seems to be (and probably is) unnecessary system bulk. Not to mention, those game demos are completely hideous, and they obscure the potentially "uncluttered" Start Menu applications tray that could be had.
Could someone perhaps offer a bit of insight, maybe even enlighten me a little bit on this topic? Thanks.
Click to expand...
Click to collapse
They can be removed in a cooked ROM, not sure if it is safe for a user to try and remove the files though. Remove one of the wrong files and you have a problem. Most of my ROMS I remove all of this stuff for the same reasons you mentioned.
i just did. everything's fine, except I accidentally deleted opera too, but thats easy to be cabbed back.
Thanks for shedding some light on this topic fellas. Great feedback. But yeah, I kind of figured that the icons could be removed from the Start Menu tray, the program files could be deleted, (with a system warning - of course) and it seems that even after that things SHOULD BE just fine.
From what I understand though... T-Mobile has made sure that some of these third-party apps cannot be deleted. For instance, I'd like to know if TeleNav and MobiTV can be rid of as well. Seriously, once freeing OUR version of the HTC HD2 of all this corporate junk and clutter from T-Mobile partnerships... it'll be very, very quick. (As if it's NOT already...)
Reignzone said:
Thanks for shedding some light on this topic fellas. Great feedback. But yeah, I kind of figured that the icons could be removed from the Start Menu tray, the program files could be deleted, (with a system warning - of course) and it seems that even after that things SHOULD BE just fine.
From what I understand though... T-Mobile has made sure that some of these third-party apps cannot be deleted. For instance, I'd like to know if TeleNav and MobiTV can be rid of as well. Seriously, once freeing OUR version of the HTC HD2 of all this corporate junk and clutter from T-Mobile partnerships... it'll be very, very quick. (As if it's NOT already...)
Click to expand...
Click to collapse
there is nothing T-Mobile has put into this rom that can not be removed when cooking. it is just a pain to find where they have implemented all the crap, some times is in more then one place the same change.
Shortcuts will be under \Windows\Start menu\Programs, related program files will be under \Program Files, shouldnt cause any issues deleting them.
jlavoie said:
there is nothing T-Mobile has put into this rom that can not be removed when cooking. it is just a pain to find where they have implemented all the crap, some times is in more then one place the same change.
Click to expand...
Click to collapse
Very true. However, would you suggest that the average Windows Mobile user attempt to dump, remove various things, then throw it all together, OR... simply use Resco File Explorer to remove the unwanted programs, system files, etc.?
I used to develop for Android, but this stuff is an entirely different ball game to me. So, I'm trying to learn the YES and NO basics here. Thanks.
Reignzone said:
Very true. However, would you suggest that the average Windows Mobile user attempt to dump, remove various things, then throw it all together, OR... simply use Resco File Explorer to remove the unwanted programs, system files, etc.?
I used to develop for Android, but this stuff is an entirely different ball game to me. So, I'm trying to learn the YES and NO basics here. Thanks.
Click to expand...
Click to collapse
cooking is the best way to remove things you do not want. a user can delete all the crap they want but this will not give them more storage (files cook in can not be deleted just hidden) but rater just hide things they do not want to see. just remember that if you delete a program, make sure nothing else uses it.
efjay said:
Shortcuts will be under \Windows\Start menu\Programs, related program files will be under \Program Files, shouldnt cause any issues deleting them.
Click to expand...
Click to collapse
jlavoie said:
cooking is the best way to remove things you do not want. a user can delete all the crap they want but this will not give them more storage (files cook in can not be deleted just hidden) but rater just hide things they do not want to see. just remember that if you delete a program, make sure nothing else uses it.
Click to expand...
Click to collapse
Alright, thanks guys. Always appreciated for a bit of feedback.
THIS THREAD CAN BE CLOSED NOW... unless other T-Mobile USA HD2 users find this in any way, shape, or form helpful to continue. Thanks again.
Reignzone said:
I'm wondering if various included applications such as the Bing widget, Blockbuster Mobile, B&N eReader, the Gameloft game demos, and so on... could be removed? SAFELY, of course.
They just create what seems to be (and probably is) unnecessary system bulk. Not to mention, those game demos are completely hideous, and they obscure the potentially "uncluttered" Start Menu applications tray that could be had.
Could someone perhaps offer a bit of insight, maybe even enlighten me a little bit on this topic? Thanks.
Click to expand...
Click to collapse
They can be reomoved but the registry has to be edited to remove some of the keys.Do one at a time and make sure the phone works ok for a few days before going on to the next.
you can do it but i wouldnt reconmmend it unless u know what ur doin but will say the each program is spidered in to the device the best sure way is to upgrade to a cooked rom but i must say but..............
WARNING U CAN CHANGE UR ROM BUT DOING SO WILL VOID UR WARRENTY WITH TMOBILE AND CAN AND WILL SPEND ANYWHERE FROM 50 TO 100 US CURENCY DOLLARS ON HAVING HTC DOWNGRADE UR DEVICE BACK TO ITS SHIPPED STATE BUT YES IT CAN BE DONE AND THERE OFFICE IS EITHER TEXAS OR CALIFORNIA I FORGET AND CAN TAKE UPTO 2WEEKS BUT I WILL SAY IT WORTH THE RISK JUST READ BEFORE U MOD........
ive deleted everything but telenav and mobitv, and no issues
Even though these programs don't show up in the Remove applications, they are able to be removed manually to release the storage--if you know where the files are located. (icons and shortcuts are easily removed).
However, whenever you do a hardware reset, they will come back, since they are part of the ROM which they could not be removed there.
I would like to both find the following 2 fixes and cook them into my rom, but i cannot yet find the fixes - perhaps someone could be so kind as to help.
1. I do not want to see the 'could not connect' message - yes I have disabled both the connected and disconnected option but cannot find a way to remove that message. Really annoying when using TomTom.
2. When I tap the little keyboard at the bottom, to bring up the on screen keyboard, half the tme I accidentally get the input option menu I never use this and only want the standard keyboard - can I disable the option menu?
I have more questions, but am working through them as I think they are solvable by me with more time research.
Many thanks.
EDIT - See post 22 for likley solution to problem 1
crazyC said:
1. I do not want to see the 'could not connect' message - yes I have disabled both the connected and disconnected option but cannot find a way to remove that message. Really annoying when using TomTom.
2. When I tap the little keyboard at the bottom, to bring up the on screen keyboard, half the tme I accidentally get the input option menu I never use this and only want the standard keyboard - can I disable the option menu?
Click to expand...
Click to collapse
1. I don't know.
2. [HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ezsip]
"EnableSipMenu"=dword:00000000
Softreset...that's it.
Thanks, but I have tried that and it did not work. (I have gone back and checked that the reg edit was still there after the soft reset, and it was.)
TomTom breaking Manila
I still cannot answer my two initial questions, but have come across a strange issue.
I have tried to cook TomTom into my ROM to save time on the install. I have done this is the past with old style kitchens on previous phones no problem.
I have used the cab to ext converter in OsKitchen and made a package. If I inlcude the package in my ROM however, Manila will not start. Itr just syas tap here to start HTC Sense, and then flickers a bit but for love nor money I cannot make it start.
By a process of elimination I am sure it is the TomTom package causing this.
Running the cab via cab does not cause this issue.
Would anyone know what the problem might be?
Cheers
Don't use the cab converter to make the EXT. My guess is that the cab has a setup.dll, and the converter is missing something important. Here is how you want to make the package:
Install the cab; get all of the files created and put them in your package. Obviously, there will be files in \program files, but there may be some dumped into \windows, \my documents, the device root or \application data or \startup. There may be a new directory in \windows. Find those files and put them in the package as well; organize them however you want. Personally, I'd relocated the .exe and dll's and anything else I could into \windows, but I've never used tom-tom and don't know how it's organized or how it works.
Next, get all of the registry keys (after you register the program). I'm guessing that it's HKCU\software\tomtom or hklm\software\tomtom or something similar. There may also be other keys installed elsewhere (like clsid keys). Find those. If there's a setup.dll, you can open it with a text editor and probably see where they are. Some may appear in the _setup.xml. The best way to do this is to track changes with sk tracker, or do it the hard way and compare the registry before and after install with windiff (comparing full registry exports).
Once you have all the files and the reg keys, build the package. Clearly, the package builder is failing you, so I'd punt on it. Don't cook in the setup.dll, though (or anyting with a similar name, like tom-tomsetup.dll; sometimes there's more than one). Also, sometimes more complicated cabs will have zip files that install further during installation-open these up, look at them to make sure you have all the contents, then remove from the package.
Just a little add to Farmer Ted's excelent instruction.
I use wince cab manager to extract a cab, this will give you the registry plus the file locations.
This will give you something to compaire and helps you easier search what you are looking for.
The file locations you can create yourself in initflashfiles.dat or app.dat
To export a registry on device I use registry workshop.
With registry workshop you can export registry from your device straight to your pc.
If you are planning to realocate all the files to windows you need to edit the shortcuts to so they direct to windows and not program files for example.
The shortcuts you can open with a tekst editor.
Thanks guys - much appreciated.
The problem is that TomTom runs fine, its just that it screws up Manila. I will try and pull the cab to pieces as advised to make sure it is converting properly and also to see if I can spot anything that might impact Manila in the registry etc.
I dont suppose you have any thoughts on teh original two questions?
Not realy, but if the cab runs fine but your package isnt then there must be something wrong in the package isn't?
crazyC said:
I dont suppose you have any thoughts on teh original two questions?
Click to expand...
Click to collapse
There is actually not much in the cab.
Using Wince cab Manager I can see no setup.dll
There are also no reg entries - nor can I find anything in the reg on the device that does anything other than list the install directory.
Looking at th files it installs, there are a couple of bluetooth files that can cause an error - odly it seems to not affect me when it is a cab but it must overwrite the windows ones when it is cooked in. The only thing I can think of is that it also has a phone.dll that presumably overwrites the one in the sys.
I will try cooking without this in my next build and see.
Unfortunately I am out of time as have recooked/flashed almost ten times trying to tie down this issue and then getting back to a stable base.
I have also 'broken' Arkswitch which was working on earlier builds. Don't think its related though.
crazyC said:
Thanks guys - much appreciated.
The problem is that TomTom runs fine, its just that it screws up Manila. I will try and pull the cab to pieces as advised to make sure it is converting properly and also to see if I can spot anything that might impact Manila in the registry etc.
I dont suppose you have any thoughts on teh original two questions?
Click to expand...
Click to collapse
It's weird that it screws up manila; I don't use manila (or T-T, obviously), so can't help you there. I'm just guessing that you're missing a registry key that you need to get the package to work. Is there a tom-tom demo (not warez)? If you post a link, I'll take a look at the cab to see if I can make an ext from it, or figure out what's going on. Some cabs are just a *****, and you're better of doing a cab install. You should see the Redfly cab, it's sick, lol. It's one that has a zip file that does a secondary install. I hate it. I also hate Redfly, but that's another story.
I read somewhere that with some sip buttons, if you press the left half, it launches the keyboard, and if you press the right half, it launches the menu. I've never experienced it myself, and don't know which builds it affects or why it happens. Is this what's going on? I'm just guessing, since you say it eff's up half the time. I have no idea how to disable the connection message, but I wouldn't mind knowing how, either. It's annoying as crap.
What's your device memory left over?
I'm just thinking, maybe you could exclude TomTom from the taskmanager exclusive list.
Sorry one more idea, you are cooking for Rhodium right?
HD2 and Rhodium have a simulair bluetooth stack.
I remember on first HD2 roms there were some problems with TomTom and bluetooth on HD2.
Just a taught.
crazyC said:
There is actually not much in the cab.
Using Wince cab Manager I can see no setup.dll
There are also no reg entries - nor can I find anything in the reg on the device that does anything other than list the install directory.
Looking at th files it installs, there are a couple of bluetooth files that can cause an error - odly it seems to not affect me when it is a cab but it must overwrite the windows ones when it is cooked in. The only thing I can think of is that it also has a phone.dll that presumably overwrites the one in the sys.
I will try cooking without this in my next build and see.
Unfortunately I am out of time as have recooked/flashed almost ten times trying to tie down this issue and then getting back to a stable base.
I have also 'broken' Arkswitch which was working on earlier builds. Don't think its related though.
Click to expand...
Click to collapse
Thanks both for your continued help.
Yes I am cooking for the Rhodium and am using the Rhodium Manila plus Cookie 1.6.1 so as to keep memory use in check. Ok I have added in the 1.8 HTC messaging but it doesn't cause a problem. Memory is about 40% free on first boot - am also using 23568 as the SYS base. I also use Ameba.
I think my Arkswitch issue is due to something else cooked in, but being honest I dont really use Arkswitch much and so am going to drop it next time I cook I think.
Farmer Ted - There is no issue with TomTom as regards Warez as far as I know - the program is fine - it is the maps that must be purchased and talking about getting round that is where the problems arise. The program itself is OK.
I might get one last chance to cook and flash tonight to check out my theory about the Phone.dll. If not I will post back and throw myself on your mercy, although as you say, it might be better to just live with the fact it will be a cab install. due to the way the files interact and the fact that the tomtom package works, I do think something is being overwritten in the cooking process and all I can see is that file.
The reason I have persisted with TomTom is that I have made an old style OEM package in the past from the cab with no problems (long lost kitchen).
With regards to the Bluetooth issues - I have sorted those now AFAIK.
RESULT! re TomTom - will post back after putting my little girl to bed.
OK - to summarise.
I ran TomTom through the cab importer within OsKitchen and it produced a package.
Although the cab had installed and run with no errors, cooking it in created 2 errors.
Firstly, there was a bluetooth message about bttray or something not being a valid application.
This is caused by two BT files in windows being overwritten by the TomTom ones. Simply renaming the two fiels to include the word OLD in the name sorted that. I will just remove them next time as I do not think they are necessary if the windows files are there.
The second issue was that Manila would not start. I believe this is due to a similar issue to the above, in that phone.dll was being overwritten. I renamed the file to PhoneOLD.dll and cooked in the package and now Manila starts.....
Still looking for answers to my first two questions though
(and yes its cos I keep hittingt he side of the button with my fat fingers that the keyboard selector comes up)
I'm not sure what's up with the keyboard, although I use Resco, so maybe you don't get then menu popup when you hit the wrong half. Have you tried killing SIPGT_app.exe? Maybe it won't pop up with that killed. If that's the case, then remove the bootlauncher key in your ezinput package. Killing it may not help, though.
I could not find that exe file to kill. The keyboard behavious is I believe as it is intended to work - just not how I want it. But are you saying Resco Keyboard fixes this?
However my final reflash last night seems to have gone a bit nuts. I am now getting all sorts of problems with apps not being able to run because they are unsigned etc or bits missing.
We are talking about stuff cooked in that has previously worked flawlessly.
Had some issues with my PC last night as well. I think I need to go back a step when I get home tonight and maybe rebuild the kitchen.
Time and kitchens have moved on a little, but as things are going well, I am back to my original 2 questions that continue to perplex me:
1. Is there a way of stopping the 'cannot connect' bubble from coming up, or even to make it automatically close after say a few seconds.
2. Is there a way of stopping the keyboard selector menu from popping up when the side of the keyboard icon is hit. I just want the qwerty option and do not want the menu to come up ever.
I have been able to make no headway at all with (1), - found mention of one cab somewhere but the link had expired - and have tried various things for (2) but with no success yet.
Anyone?
Cheers
PS- to follow up my previous posts yes the fixes I mentioned for Tom Tom work fine - it was the 3 files causing the issues.
In my old Kaiser roms i used the below reg key to disable connect notification,sorry i really dont remember if it disable also"cannot connect".
Code:
[HKEY_CURRENT_USER\ControlPanel\Notifications\{8ddf46e7-56ed-4750-9e58-afc6ce486d03}]
"Options"=dword:00000000
Disable Sip Menù is the same reg key that another guy posted here:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ezsip]
"EnableSipMenu"=dword:00000000
I tried it on my HD2 before posting here and setting it to 0 it leave the menù where you can select keypad,compact qwerty,full qwerty and language,it is still present a little menù with the option and my guess is that this isnt removable.
crazyC said:
Time and kitchens have moved on a little, but as things are going well, I am back to my original 2 questions that continue to perplex me:
1. Is there a way of stopping the 'cannot connect' bubble from coming up, or even to make it automatically close after say a few seconds.
2. Is there a way of stopping the keyboard selector menu from popping up when the side of the keyboard icon is hit. I just want the qwerty option and do not want the menu to come up ever.
I have been able to make no headway at all with (1), - found mention of one cab somewhere but the link had expired - and have tried various things for (2) but with no success yet.
Anyone?
Cheers
PS- to follow up my previous posts yes the fixes I mentioned for Tom Tom work fine - it was the 3 files causing the issues.
Click to expand...
Click to collapse
Cheers for that - I am concluding that the SIP issue I wil live with, and I already have that reg key set to zero for the connections issue, to no avail. I am experimenting with some other keys, but its really shooting in that dark, and as I cannot readily reporduce the notification, it will be a few days before I can even see any change.
Oh well. I will update if I get anywhere.
Ooooohhh, following some more digging, I MAY have an answer re the cannot connect bubble. I saw someone elses solution and that has actually led me to what could be far simpler.
I will try and cab it up later tonight for other to try. It is just a reg entry
EDIT - maybe I spoke too soon.
I am testing this by alternating between 3G and 2G on the comm manager - normally this will pull up the message. (Could someone confirm this as a valid test method).
I thought I had it solved, then the message appeared, but have done it another ten times with no hint of the message.
Some more testing to do......
Hello guys,
I have a strange problem.
I mod Jackos Rhodium ROMs (under his permission and valuable help) translating them to Polish, but I still continue to have one issue after my modifications.
Apparently my problem occurs only on WM6.5.x ROMs (currently on 21690, but before that Jackos used 28236 and the problem was there as well).
And the problem is that after some time since last SR the dialer just stops appearing after I press the "Send" button (or clicking the "Phone" link in Start Menu). After I make a SR, everything is fine for some time (sometimes 1h, sometimes 2-3 days) and out of a sudden I have to call someone and I press the Send key to bring up the dialer and... nothing happens. Sometimes only a SIP icon appears in the middle of the bottom homescreen softkeybar.
My modification is quite simple. I dump Jackos' ROMs using PRB mini kitchen which I got from Jackos (to flat dump form), exchange all the language files (mui, htm, txt) with Polish equivalents and recook the ROM adding 2 cabs to the config.txt which are used only to change some reg entries. Then I recook the ROM using the kitchen.
I reviewed all the mui files and all the reg changes and everything seems to be fine. Well, the ROM eventually works fine except for the dialer/phone canvas/SIP problem.
If you don't know what the problem is perhaps some of you can give me some advice where should I look?
I search the xda and other forums for few days and haven't bumped on any working solution...
Sorry for bumping, but I'm getting to nowhere...
I downloaded Jackos's full custom kitchen and spent 5 nights to adjust it for making 0415 ROM. I had to change many of the .mui files and hundreds of .reg, .rgu, provxml files. I decided to build all the polish packages from scratch to avoid any errors. And finally I built the ROM and besides problems with start menu structure it generally works fine. The memory management seems to be as good as original Jackos WWE ROMs (I didn't change anything in the base rom, only separated 0409 files from the packages and added 0415 packages).
But guess what! My dialer problem is baaaack...
After a SR the Sendkey works fine, but after a few phone calls it just doesn't bring the dialer/phone canvas to the front. The button itself is ok, because longpress works fine. And when I press the sendkey the light also goes on.
And the phone canvas is OK as well, because when I slide-open the keyboard and put any letter from the HQWERTY, the dialer appears immediately.
Furthermore I can now return to portrait closing the keyboard and do all the things I usually do with the dialer (put names, numbers, etc.)
Pleeeease help a poor cooking begginer because I have run out of ideas...
Stop crying and start debugging?
Use one of the tools to see the dependents of PhoneCanVas. I also suggest that you exclude all of your registry tweaks.
I'm crying 'cause I slept 2-3 hours per day since Sunday because if this @#$#%[email protected]%$
Just noticed one more thing. When the problem with the dialer happens it affect also Sense message notifications. I just received a text message and there is no "green dot" on the Sense slider nor on the notification bar. Only an SMS symbol on the taskbar.
After SR it's all good... for now...
Debugging... What tools you mean? I never played with no tools that can check the dependancy between packages...
Use the DependencyInspector by ultrashot. It's really easy to use.
Either I'm too stupid to use it or it shows nothing for PhoneCanvasEnhancement. I moved language folders in this package to the OEM way as I read this tool is for OSBuilder only, but still no effect...
Skrobel said:
Either I'm too stupid to use it or it shows nothing for PhoneCanvasEnhancement. I moved language folders in this package to the OEM way as I read this tool is for OSBuilder only, but still no effect...
Click to expand...
Click to collapse
It's designed to work with OEM packages and you're inspecting a EXT package. Try harder.
Well, the folder structure is like in the OEM package. What else should it need? a dsm? I could install OSBuilder and force it to build a dsm file for the package, but if the libraries have any dependances they should be detected by the DependencyInspector just like by the OSBuilder when building .dsm, shouldn't they?
Skrobel said:
Well, the folder structure is like in the OEM package. What else should it need? a dsm? I could install OSBuilder and force it to build a dsm file for the package, but if the libraries have any dependances they should be detected by the DependencyInspector just like by the OSBuilder when building .dsm, shouldn't they?
Click to expand...
Click to collapse
Choose what you want to inspect. You can do better than that.
Well I'm afraid I don't get you... again...
I'm trying to inspect a package. As far as I tested on other packages (in the OEM folder) the app tests all the dlls and muis it can find. And testing a kitchen doesn't make any sense with this structure and only EXT packages, does it?
Does the attached picture help you by any chance?
Heh... I should've known you never give straight answers, but you make people think. Let me dig some more...
Well... not much findings anyway.
I have changed 3 .mui files (commctrl.dll.0415.mui, shellres.dll.0415.mui, phcanhtc.dll.0415.mui). They seemed OK by the resources, but all of them have some code inside as well. Perhaps this will help.
Havent found anything in the registry. But I'm just groping as I don't know where to pay attention. The error occures usually during normal use, I couldn't find any rule when it actually happens to be able to reproduce it later on.
Either way I now use another test ROM. We'll see...
Good luck, mate.
Ehhh... still nothing. I haven't found any solution among the dependancies...
I even had a case when my dialer wouldn't have showed up right after flash (with no customisation).
But there's one additional matter. It's only the Send Key which could not trigger the phone canvas to show. When I clicked the PHONE shortcut from left softkey it showed up without problems. But the long press worked.
I started to search around for an information of the hard keys driver. But no breakthrough as well. I run out of ideas here...
Additionally I have another Rhodium (I've bought Jackos' one) and the problem is there also. So now I'm sure it's "my" PLK ROM problem, not a broken MoBo or anything else.