Paul, I remember in the original version, wasn't there a reg key to specify where the graphics are held (\phoneskin). I can't find it in the new Touch version. am i nistaken?
It is still there. I think the files are set to hidden, but you can see them with Resco, Total Commander, etc. All of the skin files are in the \phoneskin folder. Some of the SmartDialer files are kept in \Windows
It is still there. I think the files are set to hidden, but you can see them with Resco, Total Commander, etc. All of the skin files are in the \phoneskin folder. Some of the SmartDialer files are kept in \Windows
-Paul
I think you misunderstood. Instead of the files being in \Phoneskin, I wanted them to be in \windows instead. Is there a way to tell the dialer to look in windows for the dialer graphic files instead of \phoneskin?
Second question,
How do I change the color of the words "Last Call" and Connected"?
I think you misunderstood. Instead of the files being in \Phoneskin, I wanted them to be in \windows instead. Is there a way to tell the dialer to look in windows for the dialer graphic files instead of \phoneskin?
Second question,
How do I change the color of the words "Last Call" and Connected"?
The text in the box is controlled by the key: HKLM\Security\Phone\Skin\DIALER\(Portrait/Landscape)\Text\TextColor
00FFFF = Yellow
FF00FF = Purple
FFFF00 = BlueGreen
00AAFF = Orange
etc.
There is no master key to control bitmap location. Each of the bitmap references have the \phoneskin directory hard coded. You would have to change a whole bunch of keys to change the \phoneskin directory to Windows. It would be time consuming, but it would work.
Is there a .dll that contains the layout for the in-call screen? Similar to how the phcanhtc.dll contains the layout for the dial screen?
Signal,
Unfortunately, it does not. Sprint removed the calls to the layout segments, thereby disabling the ability to modify the in-call layout. I don't know why they did this, but it definately cripples the ability to skin. phcanhtc.sll contains all of the layouts, but is GSM only.
-Paul
It seems to be a problem with most of the big button dialers.
I think there is one from XDA that works (iphone) but I’m not crazy about the way it messes with the ## codes and 911, which is why I always use yours.
I have tried a base build from the 20226 and 20270 kitchens, but they both mess up the buttons (19588 worked fine).
Could it be something in the Kitchen itself that conflicts?
07-24-2008, 11:16 AM
colonel
Super Moderator Pocket PC: HTC Harrier, HTC Apache, HTC Titan, HTC Vogue....
Re: Titan 20270 GPS kitchen
Buttons are fine
Dialers are a pain in the *** as always
friguy3
Senior Member Pocket PC: 6700-->6800
Carrier: Verizon Join Date: Feb 2007
i only know of 4 issues, and they are the same for 20226 and 20270 as far as i know
1. the big button dialers dont work
2. the hard buttons need to have a cab installed and then they are fine
3. a tcpmp problem which i dont understand nor use so not sure.
4. Animation screen doesnt work, dont use it so not 100% sure
(5. oh and one other issue...you cant go backwards to 19588 )
Can you post a screen shot of what you mean by messed up? That will give me a better idea. There a a few .dlls that all work together as a set and not including one of them with cause problems.
I am getting on a plane to San Francisco in 3 hours, so I won't have much time today, but if I can see what it looks like and how it is behaving, that will give me a good starting point. We can then reverse through the registry and ensure you have the right .dlls and reg keys to reference them.
-Paul
Hmmm. I actually forgot my phone at home today...
Basically looks like it did with the EnableVoicemailIcon set to 1, with the newer sprint builds. (numbers 3, 6 and 9 obscured by multiple call history buttons).
Weak description, I know. Also the blue dialer screen seems to extend all the way across now, instead of stopping where the call history button should be.
I will post the screen capture as soon as get home.
What other info would you need to help troubleshoot? reg export? file versions?
I’m doing a search of the kitchen now for any applicable registry keys, but so far haven’t found anything obvious.
Reg keys all look the same.
I'm going to do a full base rebuild using the latest version of the buildos.
It looks like they have updated it over the weekend.
In the meantime here is a screen shot
hmm doesnt look like flickr works on this.
hang on...
Cool, thanks for the screen shot. That is a problem with the speedial. You are using speedial from the latest phones that have a different dialer layout. The dialer is fine, but the speedial app is overwriting the dialer. To fix it we need to focus on which speedial apps are installed.
My dialer does not overwrite the built in speedial, but it could to make sure it has the correct version.
Let me know how your rebuild goes and if we need to pursue this.
-Paul
No such luck.
I used the following kitchen build with the BlueFrog_Touch_Dialer.zip
I didn’t make any selections aside from the splash screen.
I think the new kitchen must be throwing something in.
Is there a way of checking to see which smartdial option has been installed?
I don't know which kitchen is adding it, but it is definately getting in there, which means the kitchen is probably use GSM dialers for CDMA phones. To do a positive test on the speedial, start the dialer, go to menu-->SpeedDial options, and disable speed dialing. Reboot and see if the dialer works, then. If it does, this will confirm it is the Speeddial from GSM phones. I can bundle the correct speeddial files up as a cab.
-Paul
Login
Panel
