Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) 071117_1 Bugs/Patches

[luv2chill]

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?

[xv6700ft]

Originally Posted by luv2chill

It's a known issue, unfortunately--with no fix at the current time (other than avoiding soft resets). From other reports it can also happen occasionally when the phone is awoken from suspend but does not most of the time.

Every WM6 ROM for the Apache has suffered from this, so if it's a show-stopped for you, unfortunately you'll have to go back to WM5 for the time being.

Would the pin problem be in effect even after the pin is entered? I eventually get into WM6, but it runs like dogsh*t.

[phuangk]

Originally Posted by luv2chill

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?

I have this hang problem on both Simple PIN and Strong Alphanumeric.
However, I can avoid the long delay problem by entering the PIN and hit the Unlock before my signal strength bar got the signal from the tower....

[xv6700ft]

Originally Posted by xv6700ft

Would the pin problem be in effect even after the pin is entered? I eventually get into WM6, but it runs like dogsh*t.

To elaborate on my problem, it takes about 2 minutes for a command to be recognized (e.g. opening the password dialogue in settings). Also, my top and bottom bars are light grey in color. It probably isn't the password but something else. Does this sound familiar?

[mbartels]

Originally Posted by friguy3

Anyone use the newer cyberon voice speed dial? When i tried it, the button on my BT headset wont initiate it. The older voice speed dial it would. tried changing some regedits but nothing, here is what i changed but nothing.

HKLM/software/oem/voicecommand/path = windows/voicecommand (sddialer with the old cyberon)
HKLM/software/microsoft/bluetooth/audiogateway/BTAGExtModule with btagext.dll and OEMAGW.dll (for the older cyberon)

I am experiencing the same thing. I can't get the BT headset to work either.

Under Voice Commander settings, I also can't get it to let me record my voice to replace the computer generated one. I record it, and get "Build voice tag failed." Anybody get that to work?

[friguy3]

Originally Posted by mbartels

I am experiencing the same thing. I can't get the BT headset to work either.

Under Voice Commander settings, I also can't get it to let me record my voice to replace the computer generated one. I record it, and get "Build voice tag failed." Anybody get that to work?

Mine worked great. recorded my voice. did commands and everything. My BT connected fine. Just couldnt get it to start from my BT headset

[phazi]

has any one gotten vibration issues>? mine just stopped working

[edufur]

still having very long sync times in active sync. takes about 1 - 2 minutes before it even starts the process, then another 3 - 20 to actually complete... depending on how recent the last sync was.

[ajgalbraith98]

Special thanks to jsavin
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

[Lazybones]

Originally Posted by luv2chill

That is correct. Believe me when (if) we manage to fix it it will show up in the changelog. I'm sorry if it's a bug that highly impacts you--we've just not figured out the cause nor fix yet.

I am just glad it is being looked into. I consider it a show stopper so I have running WM5 again. I would love to be able to try out WM6 now that the TouchFlow apps have been ported over.