Standard DialSkin - 8525, TyTN, MDA Vario II, JasJam General

hello, I have a small problem, the past days I have installed a skin dial various from the usuals and hour quualunque skin I try to install leaves the settaggi me of the previous one even if I have already disinstallato that one that gave problem to me!! Exists a way in order to restore the dial skin to that one originates them? Thanks PS: excuseme for my bad english !!

Hi, yes it is a bit hard to understand you, but I guess first off, what device do you have? if its a TyTN you can find the green dialer on the forum by searching "green dialer" or "tytn dialer" without the quotes.
Also when you try to uninstall the dialers you tried, what happens? does it not change at all, or does it become messed up..missing images etc?

hello, my device is a TyTN. has installed the DialSkin with granti keys Seen Windows type and has lost the functionalities to recall the last calls and the fast calls with the rotellina on the left of the Tytn. If disinstallo the Seen DialSkin Style and installs other Skin as an example these (http://www.zombienexus.net/portal/GL_Display.asp?SEC=3&EntryID=477) the push-buttons is all messed and with dimensions not corrected. Sorry for my English I hope you you succeed to understand

Hi again, did you install the dialer skin to your device, and not on your storage card?
I have used the red reptile skin from there before with no problems, but something definitely messed up the registry settings, not sure if the uninstall failed or what, did you power off our device, and power it back on after uninstalling the skin?
I can't be of a whole lot of help, only 4 things I can recommend you try.
1. find the green tytn dialer on the forum, install it, and it should set the registry back if the settings are included in the cab.
2. get someone with an oem tytn rom to export their dialer registry, and import it to your device.
3. Unlock your extended rom with htc tweak, and rerun the customization cabs from there again, it should just overwrite, and not create duplicates.
4. hard reset.
I could take apart one of the skin cabs you installed to see what all has been changed if you want to upload it.
All of the standard/default images should still be on your device, the only thing that could be messed up really is the registry, and possibly the phcanhtc.dll
Here's the link to the green oem dialer, might give it a try.
http://forum.xda-developers.com/showthread.php?t=287225&highlight=green+dialer

ChaoticDruid said:
Hi again, did you install the dialer skin to your device, and not on your storage card?
2. get someone with an oem tytn rom to export their dialer registry, and import it to your device.
http://forum.xda-developers.com/showthread.php?t=287225&highlight=green+dialer
Click to expand...
Click to collapse
hello, I have sovrascritto the DLL with that one originates them, hour watching in the system registry I have noticed that the keys associated to the images bring back the names of the skin do not originate them. You have said (2, get to me someone with an oem tytn rom to export their dialer registry, and import it to your device.) that a way exists in order to export the keys from a registry of one rom and to import them in my TyTN without to rewrite them all. You can dirmi as I must make?
In Attach the skin of my problem !!
Thank you

I have resolved the problem with Hard Reset the modifications brought from that one skin they were too many and they rendered the modification of many keys of the registry neccessario. A council. for how much beautiful one avoided to install it!!

Related

Dialer skin

Where can I find or make my own dialer skins? On the upgrade in the o2 active you have the ability to change dialer skins, but I can't seem to find where they are located.
Sorry zabes where are you referring to in the ability to change dialer skins?
On the XDA II I think the dialer sking is a collection of a dozen of so *.jpg files that live in the windows directory.
ed
Dialler Skin
Hullo,
Here's two of my Dialler Skins made using some excellent wallpaper from the net and V2R's Skin Creator.
Free to all, you will need to install the PSK Installer.exe from http://www.ppc-club.com/
Have Fun
Re: Dialler Skin
hshortt said:
Hullo,
Here's two of my Dialler Skins made using some excellent wallpaper from the net and V2R's Skin Creator.
Free to all, you will need to install the PSK Installer.exe from http://www.ppc-club.com/
Have Fun
Click to expand...
Click to collapse
I'm not sure if the PSK Installer can handle depressed buttons. For unknown reasons, Microsoft decided to store the skin as a set of image files - except for the depressed key, which is a resource inside a DLL. I made two DLLs for two of the better known skins. If you have access to a resource editor, you can change those to whatever you want.
This issue has been discussed in this forum earlier, use the Search feature to find the thread. And here's the URL to my two DLLs (sorry, German only): http://www.tadzio.com/ppc/index.html
Cheers
Daniel
YUP! Your depressed buttons dlls are also really good but I'm glad you popped in to make them known again.
My choice is the Candy red DLL for these skins really as it really makes the skins look good on the device.
Maybe you can help me to design some more depressed buttons in different shapes, let me show you what I mean...
In the attached image, you can see the round buttons, the problem here is that the depressed button dlls are the normal round corner rectangle shape, which makes the skin look less good on the device.
Cheerio
Howard
hshortt said:
Maybe you can help me to design some more depressed buttons in different shapes, let me show you what I mean...
Click to expand...
Click to collapse
I can certainly help you, but you can also do that yourself. You need to find a program that can edit resources inside an executable file (DLL counts as executable). Many Borland IDEs can do that, as well as Visual Studio. I'm sure there are other resource editors as well, I just don't know them.
So, all you need to do is open the only bitmap resource in one of my DLLs, edit it, then write it back to the DLL.
Again, if you want me to, I can also help you and put some images into a DLL. Just email me the images (as BMP files).
Cheers
Daniel
Thanks Daniel,
I'm going to get an editor on my machine and give it a go. Thanks for the help.
Cheerio
Howard
Got the PE Explorer resource editor which is nice.
Extracted your candy red icon file, now I just need a nice icon maker! haha
I also found that you if clear the registry setting for the depressed button, then the phone skin won't show any depressed state, while not as pretty as the depressed button it's another option.
Cheerio
Howard
1. The dialer skins above workd gd, but does anyone know how 2 change them apart from manuly, by clicling on the skin wer it is saved at my documents.??
2. Has any1 got the serial 4 V2R Skin2Chose 2.0, and if yes how can i get hold of free skins?
http://www.yorch.net/apps.htm
this is a free skin chooser
asking people for seriel nr.s in this forum is bad taste since many people who come her make programs and you just might end up asking people if they got a seriel so you can nick their software
if you use yorch's skin chooser then the skins must be put in
the dir called skin in the path you have installed the program
Ooops! lol :lol: didnt kno that I shouldnt do that! Well new member sooo!
By the way thanx the link al try now!
Actualy this is very useful n free thanx a lot, im done now, dont need 2 crack that anymore. lol
Rudegar,
Is the Yorch Skin Chooser XDA II/MS Mobile 2003, compatible?
Yes, it works great with WM2003
i av a problem with this XDA Skin Chooser, when a click on ACTIVATE a little windonw comes up sain: Activating... then a click OK n go 2 check the new skins that i apply but they not there, the original one comes up.
Any idea y??
Yep, you need to perform a soft-reset in order to actually activate the skin, mate...
I did the softreset bt still on ma original skin................?!?!
Hi, I just uninstalled the PSK Installer (didnt try any skin), but I´ve lost the Windows default skin, and I have now a new blue one.
Does any one know hoy I can try to make this change again?
I have the XDA Phone Skin Chooser, which used to work fine, but now it doesn´t change this blue new one.
Any ideas? :roll:
Thanks in advance.
Hi Buddies,
Another Dialer Skin Generator - Dialpad Maker Deluxe
http://www.pocketgear.com/software_detail.asp?id=12731
Enjoy !
Cheers,
Bong99
I've hosted some more skins and ring tones too at my site
http://www.howardshortt.com
Cheerio

Missing Bluetooth icon after using PIToday

Hi guys,
I've been playing with PIToday for a couple of days now but I noticed one thing: My bluetooth icon on the Today screen disappeard after using PIToday. The only way to get it back for me is unchecking PIToday and soft reset. This is a bummer!
I've been checking some sites for solutions but could only find the solution mentioned above and one solutions for a 3870. This was putting a shortcut to the bluetooth icon in the startup folder. In the case of a MDA II, there is no such shortcut possible. I checked the registry and Windows directory but the is no .exe file which will start the bluetooth icon. Only .dll. But I don't know where to point it to. :?:
Any other suggestions? Because I would like to buy PIToday but I still want to access my bluetooth from the Today screen.
Wouter
Even though I am a huge fan of Pocket Informant, i experienced a lot of issues with the PI today plug in and stopped using it. It may be incompatability with other software I also have installed but as well as the missing BT icon it also caused instability (lock ups) and the occassional auto soft reset.
In regard to the missing BT icon though PI today is not the only culprit. Users of Pocket Breeze from SBSH Mobile software have reported the same issue. Only way to restore it is unselect the today plug in and soft reset.
Ed
Hi Ednap,
Somebody suggested a sort of sulution for me: Using Zenphone. In Zenphone there is an option to turn bluetooth on and off in a profile. And it seems to work!
It is not the solutions but a least it is workable.
Wouter
hi,
some kind of solution
get the tool "No Plugins today" (h**p://www.ictinus.com/NoPluginsToday/)
install it (of coz)
insert into your registry a new string like this
HKEY_LOCAL_MASCHINE\init\LaunchXX where XX is the highest number of the Launch under INIT (I use "Launch90")
enter as the stringvalue the path to the tool e.g. "\Storage\NoToday\NoPluginsToday.exe" or whereever you have installed the tool
insert a link under \Windows\startup or \windows\autostart (depends of the language) and point it again to this tool. Rename the Link in such way, that it will run last (eg. "XXXNoToday")
ok, thats all, reset your device, and enjoy your Bluetooth icon
It is not a failure by any of the Today-Plugins, which make the icon vanish, it's just a timeout of the btdll, caused by Plugins, which need too much time to initialize itself, so the icon just nor appear.
What does this thing?
after reset it removes the todayscreens, the bluetooth icon appears, and after that the notoday-tool switches the plugins on again.
you need some more time (3-4 secs) after the reset, but, who cares, you got the icon back
my2cents
Dejan
Nice work, IvkovicD!
I'll give it a try and I'll post this solution also at the PIToday forum. I'm sure this solutions is a great help for Deje the maker of the program.
B.t.w I tried SnoopSoft Dash Today Advanced today to see if I like it. It is not bad. A bit slow but guess what happens?
My headset profile is now gone! First I thought it was because I had too many Todayplugins but after removing a few and soft resetting it still wouldn't come back. Any suggestions for this one?
Thanks,
Wouter
To create a shortcut to Bluetooth copy the following into a shortcut file (text file with lnk extension i.e. Bluetooth.lnk):
34#\windows\ctlpnl.exe cplmain.cpl,23
and copy it across to your PPC
My headset profile is now gone!
Click to expand...
Click to collapse
Might it be that your profile is just gone from the Today screen? Check Settings>Personal Tab>Today>Items Tab and see if Profile is checked.
Hi Mark,
No. The headset profile was not there anymore in the list. I contacted Chris Scott, who makes DashToday and the only solution he had for now, was to uninstall the program.
Not realy a good option in my opinion.... Especialy because I just bought the program because there is no trial avaliable.
For your other solution:
I want to make sure that I realy understand. You want me to make a textfile and name it i.e Bluetooth.lnk. In this file there should be the line:
34#\windows\ctlpnl.exe cplmain.cpl,23
Then copy this file to my PPC and presumably to the startup directory?
Just want to make sure.
Thanks,
Wouter
Then copy this file to my PPC and presumably to the startup directory?
Click to expand...
Click to collapse
Copy it to the Start Menu folder. It won't bring back your bluetooth icon back but you will be able to access the settings from the start menu.
Thanks,
I give it a try later.
Wouter
wouterk said:
First I thought it was because I had too many Todayplugins but after removing a few and soft resetting it still wouldn't come back. Any suggestions for this one?
Thanks,
Wouter
Click to expand...
Click to collapse
Hi,
I know this effect. I've have this "vanishing", too, if I install too much today- plug ins. Just grab your favourite registryeditor and delete some build-in today-registry entries for today items, e.g. original-task, or some of the other build in ones. If you need it (I don't believe that , make a backup, but really, do you need them?)
reset your device, the missing plugs should appear again...
Sometimes, the OS just do not display some today-plugins, if there are too much entries into registry, even, if you do not activate them...maybe at MS nobody thought that someone needs more then 5 todayplugs at once...
just joking
l8er
Dejan
Hi Dejan,
Sounds like an interesting solution. Want to give it a try but I can't find the path to the right regkeys. :?: Do you know were those keys are to be found?
Wouter
Hi Dejan,
I found the reg keys. (HKLM\Software\Microsoft\Today) and deleted the Task, Calendar and Owner Info keys. Then I did a soft reset but my Bluetooth icon didn't reappear.
Too bad.
Did it work for you?
Wouter

How Do I Install Reg Files Via a Cab??

Hello. I’m currently trying to cook my own extended rom and would like it to install some registry values from hard reset.
Is it possible to create a .cab that will insert these values??
:lol:
Cookie
[/b]
Use cabmaker or wincab or whatever it's called and just import your .reg directly. It'll make it into a cab. Can't remember what the program is called, but everyone uses it... will check it out later at home if you can't find it.
V
Cheers mate i found WinCE Cab Manager. Time To Get Cooking!
That's the one! Jeez, I think I've reached the point at which my brain can no longer be filled with new info. Seems like stuff has started flowing out of my exhaust port! The charging cable keeps falling out as well
V
Hiya - has anyone managed to set the owner info like this? I've tried a couple of different ways of getting it into cabs so that it will be set automatically on a hard reset but have not managed to make it work...
I can set other things, but not owner info, device name and start menu items, which is really starting to bug me! Can anyone help?

2 very specific questions (Disable the cannot connect bubble solved)

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......

[Q] Why HTC phone canvas does not always appear

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.

Categories

Resources