Originally Posted by obsidian440 (Post 125460)

I'm having trouble getting my direct push to work again with my exchange server. We are using 2007 with a self-signed ssl cert. On wm5 I was able to use the registry changes along with importing the cert manually to make it work. With my new upgrade I am now getting the message "server cert is wrong". I was unable to find any real answer searching google and these forums. I have tried to manually import the cert and doing the registry change but I'm still running into the same problem.

To be more specific, without the registry change, I get a message stating the server is the wrong name, with the registry it just tells me the certificate is wrong. I have checked all date/time settings on both my server and my phone, both match exactly. I have full access to the exchange server and phone.

Originally Posted by Lazybones (Post 114950)

Soft reset your device while it is enabled.. then let the password screen fully load. I tested it by just setting the password. It happens nearly every time after a soft reset, and randomly when the device is put to sleep.

Edit:

More detailed Steps to reproduce:
1. Go to settings and lock
2. Select Simple PIN as your password type and set a password of at least 5 digits
3. Soft reset your phone
4. Wait for the device to fully load (IE the tool bar theme has loaded and the phone has found a signal)
5. Now try to unlock the phone with your pin.

Originally Posted by luv2chill (Post 116753)

...yes I was able to confirm your report by doing a soft reset with password enabled (had similar lockup problems whether it was simple pin or regular password). I could never reproduce that behavior just with a simple inactivity timeout, but I know you said that was random. But it definitely occurred after every soft reset.

I flashed back to every iteration of helmi's wm6 ROM I had and they all suffered that issue. Seems to be some sort of timeout issue... like the device is waiting for "something" once you click unlock, and when it doesn't happen in x amount of time the device gives up and proceeds anyway. That's what it "seems" like anyway--I could be way off base.

I had helmi confirm that it does not occur on the Universal (which is the closest device hardware-wise to the Apache). So it's either a driver issue or something in the registry that's causing it. Hopeully we'll get to the bottom of it soon.

Originally Posted by luv2chill (Post 125027)

Hmm I saw the same hang whether I did Simple PIN or Strong Alphanumeric. Have others been able to solve this by choosing Strong Alphanumeric?

Originally Posted by spetrillo (Post 117955)

I have just flashed my phone from the new kitchen and noticed that the battery meter in the upper right portion of the phone does not work. When I tap on top of it then it should take me to the battery meter but it does not. This used to work in the VZG kitchen.

Originally Posted by luv2chill (Post 117817)

It's due to HTC Task Manager (X-button) IIRC.

Originally Posted by Wizzard (Post 124654)

The only problem I have now is with the "Boot Splash." It seems to have a greenish tinge to the picture, even though it is black and white! I used the converter to save it and it worked better than just a plain .jpg, which was all green.

Originally Posted by gguruusa (Post 126483)

Ok, turns out it was broken for both converters, and I had only fixed one before. New build has been posted.

For the curious, it's actually a bug based on the low order Red color bits. Windows manipulated the pixel value on my behalf in order to distribute accumulated error when moving from a low color depth to a higher color depth. My logic assumed the pixel value I put in would be the pixel value I got out (sounds reasonable, doesn't it?), so when it wasn't things went awry. You see the artifact as green because the low order red bits were writing on top of the high order green bits. By pure chance, green does not write on blue because of an election I took in the code. Blue doesn't have a color after it to overwrite. So, the only color getting messed up is green, which explains why all the artifacts were green.

Originally Posted by reeg420 (Post 128016)

PocketCM doesnt show the touch skin. It showed up by default in earlier oem rar file. I opened the files up and it shows both touch and theme as cmt files but doesnt show in themes setting in CM.

I ended up just using the oem files from the earlier one which had the skin since most of the newer oems in there I dont use anyway.

Originally Posted by Kolano (Post 128122)

Yes, it appears that the latest kitchen updated to PocketCM .16 (development). In my case only the "Black" and "White" skins seem to do anything, all other themes result in the "White" theme being used.

I'm not sure yet if the issues seen are due to a partially implemented OEM or the developmental status of .16 as of yet. Since we missed listing this in the changelog I'm guessing the former.

Originally Posted by alpine (Post 130362)

I've had major conflicts with the HTC Home plugin and the HTC task manager from the kitchen (both versions). When I boot up the system hangs when I press the task manager X. This only happens when the Home plugin is installed.

To get around this I installed HTC Home v2.1.1005.722 and the updated Home DLL that removes the ID check for it to display on the Today screen.
cab here:
http://forum.xda-developers.com/show...=v2.1.1005.722

Updated DLL here:
http://forum.ppcgeeks.com/showpost.p...&postcount=146

Updated version by BtT with the modified DLL included:
http://forum.xda-developers.com/show...&postcount=191

Originally Posted by ajgalbraith98 (Post 125169)

Special thanks to jsavin http://forum.ppcgeeks.com/images/sty...er_offline.gif
Junior Member

Pocket PC: XV-6700
Carrier: Verizon

Who took me to SPB Club where my poking around got the answer that the PocketPlusTouch.dll is repeated in two spots
(I thought it was a mistake and got rid of the wierd one..thus causing the bug of no smartscrolling)

The fixed OEM in all it's glory is at http://www.ajgalbraith98.com/ppcgeek...1_11-18-07.rar

Also if you would like it to register your key number open the folder and
then the RGU file and find [HKEY_CLASSES_ROOT\CLSID\{0B9E877C-7ECA-4790-9BE3-EE1F2566BEF8}]

Add the following DIRECTLY under that line
@="Spb Buttons Extension"
"APISet"="YOUR-CODE-WITH-DASHES"
"Application"=dword:a9401b68
"Version"=dword:00000000

and bake away

also

SPB Plus 4.02 is comming soon with bug fixes, so please be aware that if you feel it locks up your today screen, it's not my OEM...

--ajgalbraith98