I'm trying to change the theme on multiple devices programmatically. I'm using server scripts to do this.
I'm currently testing with a HTC Universal (WM 5), a HTC Elf (WM 6) and a HTC Diamond (WM 6.1). All still have the original Rom at this moment.
I made a custom theme that I will call "MyTheme.tsk". I'm aware that we're dealing with different screen resolution devices, but the script detects this first and sends the right resolution theme to each device (confirmed to work correctly).
This is what I'm doing (got it from examples on MSDN):
- Send MyTheme.tsk to mobile device
- Delete reg value: HKCU\Software\Microsoft\Today\UseStartImage
- Exec: \Windows\wceload.exe /safe /noui /nouninstall /delete 0 \Windows\MyTheme.tsk
- Set reg value: HKCU\Software\Microsoft\Today\Skin MyTheme.tsk
Every event is being logged and none gives any errors. However, the theme is not applied on any of the devices at all. The only thing that happens, is that the theme is highlighted if I go manually to Settings - Today.
As an alternative, I tried replacing the Exec event by the following:
- Exec: \Windows\CusTSK.exe \Windows\MyTheme.tsk
This results in a successful theme change on the WM 5 device. However the WM 6 & 6.1 devices change all color settings successfully, but don't apply the background included with the theme.
I tried to add an event to force a refresh of the Today screen, but that didn't change anything. The stwater and tdywater files in the Windows folder simply aren't replaced by the right files.
I know I can simply make a script to change those files manually, but I rather find out why this isn't working the way it should. According to sources I found, it should work using "wceload.exe" which didn't do anything in my case.
The theme itself is not the problem, I tried using the same script to set the device from a custom theme back to the default WM theme, with the same results. Also, manually applying my theme works just fine on all devices.
All 3 devices have been hard resetted to set them to factory defaults, without any changed settings or installed applications except the application that receives the settings from the server.
Anyone has an idea why this isn't working?
A little note: MSDN says I have to delete the UseStartImage reg value. However doing this doesn't seem to make any difference, because it is set back automatically unless I manually enter to remove it in the tsk file settings.
Finally found a solution. Although it's a bit weird.
Apparently it only works with CusTSK when the background files are GIF files. They can be any format (JPG, PNG, BMP) but have to be renamed to GIF for it to work.
Related
Ok... I've been playing with this for a week or so to no avail.
I wanted to Disable & delete the standard KB from the device & replace it with my copy of FingerTouch or VGAKey & after failing it's now become a ROM cooking issue.
I started out trying just to delete the default KB from the registry. I've found the association {42429667-ae04-11d0-a4f8-00aa00a749b9} for the module msim.dll. But whenever I delete this, like I do with Block Recognizer, or if I install one of my other KB & try to change this entry to be associated with FT or VGA KB, my device freezes at the Animated Boot screen & requires a hard reset.
Being unable to disable or delete the key without devastating results, I decided to try & cook out the default KB & replace it with one of my alternatives. So far everytime I still get stuck at the boot screen.
I know (I think I do) all of the default KB files & associations. In windows you have msim.dll (icon & improc I believe) & msim.96.dll.
In the registry I've found HKCR\CLSID\{42429667-ae04-11d0-a4f8-00aa00a749b9}, which handles the display & selection in the KB input selection pop-up. I've also found the HKCU\Control Panel\Sip\Default Im reference to {42429667-ae04-11d0-a4f8-00aa00a749b9}.
Everytime I attempt to change these value to another KB or delete them in the registry of any ROM installed I get a fatal error that won't allow for the OS to fully boot.
When I try to alter this info in a rom I'm cooking, I also get this fatal error for which the only way to recover from is a hard reset & flash to a ROM that has the default KB still intact.
Does anybody know what I'm missing???? I don't see anything in startup that is calling for the Default KB, so I can't seem to understand what's causing the freeze up.. Any of you pro's out there know what I'm missing or why I can't get the OS to boot without the default KB?
Can you delete or replace the default KB completely in any device ROM from the registry? Can you remove the default KB from a cooked ROM? If so what am I missing? After a week of trying I need help!!!
Thanks for the help.
NOBODY??? Not one of you have ever tried replacing the horrible MSIM KB with something more useful????
I never really tried to uninstall the default one. I've only replaced it with a colorized one. I know you can install another one and have it set as default SIP, but I haven't tried since I haven't really liked any SIP that's been perfected enough to cook in...
Sorry I can't be of more help.
Some thing here I never have found something better to cook in. I use the grey colored KB since it looks the best with the HTC .tsk but thats just a matter of cooking in the right .msm file. Sorry I cant be more of a help.
I don't know if any of you have ever noticed this, but even if you use another KB & assign it as default, the standard default KB still retains the Default IM status. The only way a change to KB default status can be made is to inject a start up entry that redirects.
If you set another KB as default, all the tools, sk, etc... Still all show the STD KB as also being default & so it cannot even be disabled. Weird.
GSLEON3 said:
I don't know if any of you have ever noticed this, but even if you use another KB & assign it as default, the standard default KB still retains the Default IM status. The only way a change to KB default status can be made is to inject a start up entry that redirects.
If you set another KB as default, all the tools, sk, etc... Still all show the STD KB as also being default & so it cannot even be disabled. Weird.
Click to expand...
Click to collapse
Yep, and "sipchange is the cure"
Create new package and cook it to your ROM.
[email protected] said:
Yep, and "sipchange is the cure"
Create new package and cook it to your ROM.
Click to expand...
Click to collapse
SIP Change doesn't always works.
AllTheWay said:
SIP Change doesn't always works.
Click to expand...
Click to collapse
Hmm, I cooked few versions of WM6.0 and never had a problem. Sipchange always worked for me. Maybe I'm lucky
Didn't try with WM 6.1.
SIP change changes what pops up as the default, but does NOTHING to change the actual system setting as msim as default. It allows for overide, I know, I use it, but you still can't remove or disable the msim KB. The point is to cook in something useful & remove unnecesary images & resources, not to add a tool to do something that several other proggies I already use can do. i.e. SK Tools also allows you to default other KB's.
GSLEON3 said:
SIP change changes what pops up as the default, but does NOTHING to change the actual system setting as msim as default. It allows for overide, I know, I use it, but you still can't remove or disable the msim KB. The point is to cook in something useful & remove unnecesary images & resources, not to add a tool to do something that several other proggies I already use can do. i.e. SK Tools also allows you to default other KB's.
Click to expand...
Click to collapse
I know what you mean, it would be better option of course, but for now I didn't find solution.
Wondering if this is part of Windows Mobile 6.1 or something, I'm using the latest stock rom from ATT, on an ATT Fuze 5.11 I believe, and when I have TouchFlo3D disabled, and I am just using regular Windows Mobile's today screen, any background I apply on any theme, always whites out the background for some reason. As in you can still make out the image, but it's like a white overlay was put on top of it. Is this part of Windows Mobile 6.1? I couldn't find anything on it.
There could be a transparency set, but I'm not quite sure how you did that.
Anyways, if you open up "Pictures & Videos.lnk" from \Windows\ and pick your image, set as background, and it will ask you to set the transparency level. Set it to 0.
There may be a registry setting you can change, but I'm not sure where it is, if it exists.
Oh, thanks. That was it. I was setting it through Settings>Today and not through the Pictures and Videos program.
I am trying to reskin the dialer of an iPaq hw6945. I'm having trouble with the default background. I've tried any number of skins and skinning tools and none seems to change the default blue backround.
My first thought was to simply replace the background image. On the iPaq hw6945 that image is "dlrback_sqre.png". Unfortunately that seems to be a ROM image so even if I change the file attributes, I can't replace it.
Any ideas?
try making the files into a .cab...
How will that help and how would I do that?
I tried to install a couple of different dialer skins, an SPB dialer skin, and one of the DirkGently dialer skins. The former used a PC based exe installer the latter a cab. In both cases they failed to install their backgrounds. The buttons installed just fine but the background didn't change. So I thought I'd "hack in" the background.
So far I haven't been able to do it.
I unsuccessfully attempted the fore mentioned image swap, then I went poking around in the registry.
I found "dlrback_sqre" in two places in the registry. I replace those values with "dlrback_square" the name of my image in the same directory, but that didn't seem to do a thing.
Moved as not theme release.
Sorry... new to the board. I thought this would be the place to post.
Thanks bilbobrian for your help. It lead me in the right direction.
You're right all it took was a signed cab (and a background image with right name) to overwrite the background. I took one of the DG skins opened it with a cab editor and inserted the right file.
When I get some time I may just make a set of custom skins. I already know how to do the calculator, and WM player, although I might just make a skin for Coreplayer which I use more often. TCPMP was a such a great application, I decided to spring for the licensed version.
Hope to see the results of your work!
Good luck
Hi
I was wondering what i takes to change the text color in the startmenu in a WinMo 6.5.x installation.
The registry method with color 39 does not seem to work anymore. I also tried a SK tool but no success either.
Anyone with some tips?
I too have a problem with WM6.5...
I have a HTC Touch Pro II which i have upgraded from the Touch Pro and its a far better phone, but i keep having menu text colour problems...
Basically, i created a theme for my old phone and installed it on my new one and it worked for a few days, then the menu text which started as all white, stated changing to black for some of the icons - not all, but a few days later they are all black, and on my black background its impossible to read...
So i changed the theme, all text again 2 different colours! different theme same thing :S
So went to the MS theme maker software which to cut a very long story short, finally managed to get a theme from the site and saved on my phone!
Success! untill the phone was reset and now its 2 colours again! this really doesn't make any sence...
So 1) why are there 2 different colours setup for the menu text? and is there any software which will let me edit all the colours for themes on my laptop then upload to the phone?
Thanks guys - this is driving me nuts!!!!
I Know This Thread Is Dead But This Will Help People Like Me Looking For A Fix
Here's how to change the Start Menu Text color:
*SAVE A COPY OF THE FILE YOU'RE EDITING SOMEWHERE IN CASE YOU SCREW SOMETHING UP!
1. Extract the file StartMenu_GridScene_480x800.cpr from your Windows directory to your desktop.
Mine includes 480x800 at the end because that's my devices resolution(Touch Pro II). If you have a different resolution, I'm pretty sure it will have that at the end of the file name.
2. Open the file on your PC with Notepad.
3. Find every occurrence of ForeColor="#00FFFFFF". Mine had two.
It might not be 00FFFFFF, but that's hex code for white so it probably will be.
4. Replace 00FFFFFF with whatever color hex code you want.
You can find any color's hex code online through Google.
5. Copy the edited file back into the Windows directory of your phone. Click yes when it asks if you want to overwrite the file.
6. I soft reset, though I don't know if it's necessary. I figure it can't hurt.
7. Check and see if it worked.
I've attached my .cpr in a ZIP file for BLACK Start Menu text. It works on my Sprint Touch Pro II, and it should work for others but it's still not my fault if something goes wrong. If you use mine, STILL SAVE A COPY OF YOUR .CPR IN CASE IT DOES SOMETHING FUNKY!
moved to the right forum, please post in the correct forums.
Hi,
Back in the time, when i was using Yuki's ROM for HD2 there was two themess called 'aero black' and 'aero rich'.
Does anyone know if, i can get then on Mango 7720.68?
As i think it is only about adding a new folder and the key and values in the registry.
Maybe with a CAB installer, or adding amnually, but current regeditor can not add things, it is only capable to deleting entries.
Thanks
SOLVED!
Hi Folks,
I tried an "old" nodo registry hack and changed the "ChromeColor" value to #00000000 in the dark theme, so full transparent and it works. Some menus and calling buttons background became transparent. Nice.
changing "Pagebackground" value doesn't work do not do it. I think it is because the same reason why transparent background also doesn't work on mango.
So it is not compleme yet, but i will keep discovering this part of registry. I hope someone else also likes this.