Hi, wonder if anyone can help, ive installed duttys dialer skin (which is great by the way) but the issue i have is when i dial the number and it is connecting the text is all in black, which is difficult to read, how can i change this too white ?
Ive tried using the UI tweaker, even changing entries in the reg but nothing seems to work. I sure i read something regarding this a while a go, but for the life of me i cant find it agian...
thanks
taz
I had exactly the same problem... I think it must have been a glitch when dumping the dialler to a .CAB.
I tried using Schap's Advanced Config (search for it) to disable *all* dialler skins, which reset mine back to the Windows Mobile dialler, which uses bold white text on a grey gradient. Looks a bit iPhone too.
I got fed up with that, though, and got the real deal - I flashed my phone to the HTC Asia 1.31.707.09 ROM. This gave me the original HTC dialler, which uses white text on the same gradient (the buttons are easier to read, too).
I'll admit that was perhaps a little extreme, though.
Yeh I had that problem.
Just backup your current ROM in case of warranty issues and flash something like Tom's ROM or and official HTC Rom. They're quicker than the stock ROMs anyway.
Hello, I was wondering if someone, maybe dcd himself , could explain to me why the Vogue dialer from his kitchen does not have different graphic files for each button and each action (up/down)?
I'm trying to use the skins from this thread
http://forum.xda-developers.com/showthread.php?t=372098
I've currently put the numbers on the background image but I can't use the pressed animations.
These skins suppossedly work on the Touch (which IIRC is the Vogue) and someone in that thread even said they work on the Mogul. Should I have chosen the titan335 dialer in the kitchen?
Thanks ... and as always props to dcd and company for his work.
Not sure if this will work for you but when I run the kitchen I DO NOT select any dialer. This will install the standard WM6 dialer then I install the cab for the dialer I want after the phone is up and running. I made a custom dialer to match my matrix theme and never took the time to OEM it. Works fine when I do it that way. To be honest though I'm not sure about the animations you are speaking of.
Thanks for the reply. The animations I'm speaking of are the different images for a button pressed and not pressed. lllboredlll what optionsdid you choose when you compiled your carrier images in dcd's 3.01 thread? I tried your Verizon one too and it didn't work. Thanks.
gimpdog said:
Hello, I was wondering if someone, maybe dcd himself , could explain to me why the Vogue dialer from his kitchen does not have different graphic files for each button and each action (up/down)?
I'm trying to use the skins from this thread
http://forum.xda-developers.com/showthread.php?t=372098
I've currently put the numbers on the background image but I can't use the pressed animations.
These skins suppossedly work on the Touch (which IIRC is the Vogue) and someone in that thread even said they work on the Mogul. Should I have chosen the titan335 dialer in the kitchen?
Thanks ... and as always props to dcd and company for his work.
Click to expand...
Click to collapse
He is essentially using an alternative. It doesn't seem as he is using the original TOUCH dialer because it might conflict with some Mogul / 6800 operations and is using an alternative.
Search for Mogul Big Button Dialer. This is closer to the dialer that he uses in his ROM's.
It essentially looks like the Touch dialer but you cannot assign skins to the keys when they are pressed. But you can skin the entire dialer.
You are free to install a true Touch Dialer or even the CAB that is called WizardRetouched. These are all alternatives, but conflict with some features on your 6800.
check out this post for more info on the Mogul Big Button Dialer " post 8"
http://forum.xda-developers.com/showthread.php?t=378225
Here is a pic of my dialer that I use on top of the Big Button Dialer CAB.
gimpdog said:
Thanks for the reply. The animations I'm speaking of are the different images for a button pressed and not pressed. lllboredlll what optionsdid you choose when you compiled your carrier images in dcd's 3.01 thread? I tried your Verizon one too and it didn't work. Thanks.
Click to expand...
Click to collapse
All those had the vogue dialer.
Unfortunately this is only a workaround but it is an effective and easy solution to an irritating problem ! the idea is to change the background out for a white one so the black text shows !! to that end I have included all the files you need to sort this out !
all you have to do is use the reg editor (task manager) included with ap 4.0 tap on the process's tab and kill a process called cprog.exe (this runs the phone service and has access rights to the files you want to modify). After that copy the included files into the windows folder, i did it whilst using active sync) through browse mobile device on my computer for simplicity after editing the pics.
I am also including the originals incase you want to go back !! of course this is now opening the door for any manor or wonderful custom backgrounds for the dialler screen, and infact a whole host of other HTC software including the mp3 trimmer, which also has it's "BG" pics in the windows folder.
anyone who is running 96dpi like me will have noticed that there is space at the bottom of the dialer pad that allows you to see the app running behind the phone, this is now easy to fix and requires these files to be modified in size to cover the currently vacant area, although idealy we need to work out a way to make the bars twice as large in 96DPI to make them finger friendly !
If get round to it I will make the adjustments for 96DPI but it is good as is for all resolutions
and here are the originals
i think the cab you have is bad. i remember i uploaded the addons with a manilla cab that was a bit messed up and i think the text there was messed up. a few min after i uploaded a fixed addons rar.. the text should be find in the new addons cab. i remember i used it to before and there was no text problems.
Pawel062 said:
i think the cab you have is bad. i remember i uploaded the add-ons with a manilla cab that was a bit messed up and i think the text there was messed up. a few min after i uploaded a fixed add-ons rar.. the text should be find in the new add-ons cab. i remember i used it to before and there was no text problems.
Click to expand...
Click to collapse
Ho hum, that took me ages to do and was quite clever by my standards. I only upgraded to AP4.0 yesterday, as I was waiting for a fix to downgrade the SPL on my last ameo before sending it for a warranty repair, in the end I could not wait any longer and just chanced sending in my old phone, which is good, as I now have a new phone
all this is relevant to what you said because I downloaded AP4.0 and the add-ons as soon as they came out, and have not really sifted through the thread because it is huge!
mental note to self RTFM, I could have spent my time productively going through the thread instead of inverting colours in paintbrush !
i'm having a little trouble getting my volume adjustment bar to change back to the original silver color on my sprint touch pro. i installed a coke theme using Diamond TF3D config and it changed it to red. can anyone help me get it changed back?
i have tried using the return to default option in TF3D config
Any luck??
I am having the same problem,
Have you found the answer?
no i haven't. i wish someone would take the time to help.
I can't even get the Diamond TF3D to run on my Sprint TP...
You have to go to /programfiles/tf3dconfig/ and delete the "Tweaks.xml" file then it should work.
download this theme file and change your theme to it with tf3d config it should take your theme back to the original way: http://thetouchblog.com/tf3d/themes/Elvelynn Black Red/black_red_complete.theme
In my cooked ROM, I'm having a problem with the font on the HTC keyboard, and on the screen that comes up once the device is plugged into the computer (to choose between Activesync, Drive, and Internet sharing). I've found similar problems searching and tried applying those solutions, but I haven't come across exactly this:
When TF3D is disabled, the font for the keyboard and "Connect to a PC" screen drops out to Courier (and I've confirmed it is indeed courier, not just something that looks like it. When TF3D is enabled, they look fine.
I'm also reasonably sure I saw instances on my earlier build where the landscape of the keyboard would be fine, but in portrait mode, the font would drop out.
The solutions I've found in my searches suggested adding certain aliases under [HKEY_LOCAL_MACHINE\SYSTEM\GDI\V1\FontAlias] in the registry. That hasn't helped. I've worked around the problem by copying one of the HelveticaNeue fonts (LT 35 Thin, I think) over cour.ttf in the windows folder, but I wouldn't be surprised if this has unexpected consequences in other applications.
The ROM uses a Fuzeberry-themed version of TF3D1.
The following fairly common HTC apps are omitted from my ROM (cooked with Da_G's 21500 Test 2):
HTC Comm manager (because I used a Rhodium version instead)
Enlarge Start Menu
Enlarge Title Bar
HTC Dialer
HTC Volume
TouchFlo (not TF3D, just TouchFlo)
HTC Startup screen
I -have- included HTCFontLink (Rhodium version, which is what comes with the kitchen). I have also made sure every TTF available in the kitchen is installed to the device. That includes: cour.ttf, HelveticaNeue LT 35 Thin.ttf, HelveticaNeueOTS.TTF, tahoma.ttf, tahomabd.ttf, wingding.ttf
I find poking around the registry that there are several entries telling HTC apps to use "HelveticaNeue LT 55 Roman," which isn't installed. But there's also an entry under [HKEY_LOCAL_MACHINE\Software\Microsoft\FontLink\SystemLink] that appears to alias that font to tahoma, which is installed.
Any insights?
I followed the below instructions, and it fixed it for me. I could probably make a cab for you, if you'd like (I have these fonts saved to my Storage Card)
Trancecoder said:
To get the proper fonts to display in USB2PC, as well as the HTC keyboard, you need to grab 1e8c4d7d_manila and 6582c9b1_manila, rename them to their proper names (just add .ttf and open them with the default Windows Fonts thing), and add them to \Windows\Fonts\.
Click to expand...
Click to collapse
EDIT: Just in case you want to try it, I've attached a cab with the font files, that will copy them into the Fonts folder. LMK if it works.
EDIT2: Per your request, the font files are attached in a zip file. Perhaps the cab will help others who are running a no-manila ROM.
EDIT3: I appear to be one step behind you at every post, lol. Ah well. At least that wasn't really any work for me .
That would be great (or even just a zipped copy of the fonts themselves, no need to cab them up for me).
Oh wait, I just realized where you mean to grab the manila files --as in from my existing install (or kitchen). Never mind -- you don't need to do anything, I can grab them myself. Thanks for the tip!
EDIT: Hah - As I was typing this, you got up both the zip AND the cab! Thanks for such a quick response, and for the upload. Gotta love XDA!
Hi, I thought I updated htc fontlink with the missing font (HelveticaNeue LT 35 Roman.ttf)
It's there on my end, did I forget to upload?
Da_G said:
Hi, I thought I updated htc fontlink with the missing font (HelveticaNeue LT 35 Roman.ttf)
It's there on my end, did I forget to upload?
Click to expand...
Click to collapse
I think 35 was there, but not 55 -- this is as of 21500 Test 2. Haven't ventured into new-kitchen-territory yet
I haven't seen 55 in use, which program uses it?
It seems that the "Connect to PC" screen does (and likely the keyboard, but I can't test that since I'm running a version of my ROM that omits the HTC keyboard).
When I used FontCreator to rename a copy of Tahoma Bold (new filename "neue Helvetica LT 55 Roman.ttf", new font name "HelveticaNeue LT 55 Roman) and copied that into the windows folder, it used that for the Connect screen.
Both 35 and 55 are included in the cab Captain_Throwback put up.
Like I said, I think I noticed (in a previous build where I was using the HTC keyboard) that it looked right in landscape, but not portrait. So I wonder if it's possible the keyboard uses 35 in landscape, and 55 in portrait. Not near my home machine or phone anymore to take a closer look.
Does the system register those manila files (which are just TTFs in disguise) as fonts only when TF3D is running, and that's why we need to use these copies the rest of the time?
Yeah, manila registers the fonts when it's cooked in...
Although, both the HTC keyboard and usb popup are using the 35 font on my end, don't have the 55 font installed, or touchflo3d, it uses tahoma when 35 isn't installed..
I do see that they specifically call for the 55 font, but seem to use 35 fine without it.
Just an observation
That's odd, because on mine it definitely was using 55, at least while TF3D is off. If I had a 55 (even if it was another font renamed), it used that. If I had no 55, it used courier. 35 was definitely installed and available.
I wonder if the behavior is different when TF3D isn't cooked in at all than it is if TF3D is cooked in, but disabled. Or maybe if there's something specific about the TF3D package I used. I'm at work, but I'll take a closer look at what it's putting in to the registry later.
Good news is, the cab works like a charm.
Wordsmith9091 said:
That's odd, because on mine it definitely was using 55, at least while TF3D is off. If I had a 55 (even if it was another font renamed), it used that. If I had no 55, it used courier. 35 was definitely installed and available.
I wonder if the behavior is different when TF3D isn't cooked in at all than it is if TF3D is cooked in, but disabled. Or maybe if there's something specific about the TF3D package I used. I'm at work, but I'll take a closer look at what it's putting in to the registry later.
Good news is, the cab works like a charm.
Click to expand...
Click to collapse
I found it works fine on my diamond rom if Manila is cooked in wether it is enabled or not - connect to pc screen, ezinput 1.5 & volume control use the correct 55 font however if manila is not cooked in the rom I had to add the 55 font for them to appear correctly and not as courier. The rom already had 35 cooked in from htc fontlink. Hope this helps