Has anyone been able to locate a workaround to scroll using the volume buttons? NOTE: I did search before asking this question.

I use iSilo to read books/magazines (WT Library here - anyone else using that, haha), and in WinMob 5 I used to be able to scroll using the volume buttons. That no longer works in ANY application using WinMob 6.

Here is the link to the forum for fixing MS Voice Command 1.6 announcing calls to speaker and BT device.

http://forum.ppcgeeks.com/showthread.php?t=9239

Yep, now I only open it back up if I need to install or upgrade something in there. Perfect!

That's the smartskey app. See this post by luv2chill: http://forum.ppcgeeks.com/showthread.php?p=21140

I installed the new htc x button task manager 2.0 located here:

http://forum.ppcgeeks.com/showthread.php?t=9144

I have experienced much better performance out of wm 6, i.e., much more responsive, snappier, no more sluggishness. I'd say it is a 4x increase in general performance.

anybody confirm?

Also, anyone come up with a fix for the fullscreen landscape media player bug yet? This is an annoying one to me. I haven't noticed anybody working on it on these boards. I hope we all can come up with a fix before the kitchen is released. I tried poking around in the registry a little, but this is really a bit over my head as I consider myself just a power user. Anyone?

Hi,
am new to this website and have got to say that you guys are great. i have the ppc-6700 through sprint and almost traded in until this upgrade.
I have come across 2 problems that i was hoping you could answer:
1. i have to log into work through a secure website and this used to work but now it states "The website you want to view requests identification. Select the certificate to use when connecting" and gives me an empty box. I tried to import the same certificate that i use on my laptop and it installed the *.cer into the intermediate section of the certificates but still doesn't work. any ideas
2. All my versions were previously updates prior to the upgrade with
radio version 1.41.00
prl version 20229
pri version i think it was 1.19
now i am back to:
radio version 1.12.00
prl version is updated
pri version 1.16_003

i am not too woried i guess about the pri version from what i have read but was hoping to update the radio version. Read all the threads on this website i could find and tried to install the phonex06 radio 1.41 but i got an error 150. Does anybody know how to correct this for the new apache wm6??
thanx in advance

love the new rom!

but I got 1 problem.
I have sprint/ppc6700
when i'm on the phone for about 1-2mins the call just drops.
it looks like the evdo goes off and it switches to 1x when it drops, but not sure.

i tried to do the evdo always on registry fix:
Try changing the value of AlwaysOn from 0 to 1:

[HKEY_LOCAL_MACHINE\Comm\ConnMgr\Providers\{7C4B7A3 8-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections]
"AlwaysOn"=dword:00000001

I do not have a always on in that section, just phone as modem, and sprint pcs vision, which i changed the alwayson to 1 in the sprint pcs vision/alwayson key but still no luck.

I have did a hard reset 1 time, still no luck. After changing the registry I have tried soft resetting and the values do stay put.

any suggestions?

just did the radio update (v1.4, which I had 1.21), with the wm6 it wouldn't bootup after I installed the rom, but I did a hard reset and it came up fine.

I'll have to test this out and see if it helps any.

After the hard reset, before the sprint software installed I did a soft reset, which I did not do when I first installed the wm6 rom.

nope... still drops calls
anyone have any suggestions?

I need to figure out how to go back to the standard roms... I want to set my phone back to stock and go from there.

To get back to the stock Sprint ROM, run this file:
http://www.utstar.com/pcd/downloads/...0_WWE_Ship.exe

I'm not sure why your phone is dropping calls, but I can say that it doesn't have anything to do with EVDO. EVDO is for data transmission, not voice. Do you live in the boonies? Is there a chance you just have poor coverage where you are?