yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
No, not that I know of at this point (at least not in the default application) a regedit or even a different customizer may allow it, none I know of directly but I can look into it more when I have some free time unless someone else knows a direct answer for this

Search this thread directly and you will find a link to the page, but really from the issues Ive read, stick with the MSN weather (just a personal opinion) until some more tweaks and issues have been ironed out

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
The fix for the date being cutoff was discovered and corrected by HTCToucher on this

POST

with the needed file edited and posted the fault size was not an issue

Wasnt sure you saw that being posted so just making sure the data is there for those having the issue to begin with

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] axemurderer:
I don't know about anyone else but, I have also tried all of the QPST, Tellus settings to no avail. My GPS today is woking with instant locks. I am in NYC and it is cloudy. Here is what I did this morning after weeks of evey other setting and Various roms. Flashed to NFS 6.5 V62 Rom, install his GPS cab file and tested = NO GPS yet.. I then went into phone settings, services tab and changed the location setting to, 0ff, 911 only and soft reset. After restart, changed location setting to on, ran GPS viewer and instanly picked up 5 or more sats and locked. GM and LS working great. Not sure how long this will last or if this is working today for anyone else. Please post back.

Current radio is 3.37.77

History = 6900 with stock Wm6.0 updated to official VZ6.1 R3.37.78 ran vahalla GPS worked.. Pre VZ kabash on GPS. Then downgraded radio to Sprint rom R.3.37.77, then most NFS 6.1 and 6.5 NO GPS till Today...
[Touch CDMA Windows Mobile ROM Development] suntopper:
OK, VZW users don't get your hopes up because what I'm about to say is for the most part just a repeat. As some of you know last week my phone was (apparently like others) getting very unstable. After getting some good advice (as always here), I flashed back to the VZW update with radio 3.37.78. I wanted to wait a while to make sure my phone was back to normal before posting so here goes. First my phone is running as good as ever. I don't know why reflashing to a stock rom fixes this (yes I've read the posts), but all is well with the world again.

My sequence of events: 1) flashed to VZW rom (RUU_Vogue_VZW_WWE_3.14.605.1_Radio_3.37.78_Ship.exe), let customizations run; 2)followed the instructions from thermus on pp 140 (post 1311). After I unlocked with 2.31 the phone appeared to hang. I put it into bootloader mode manually and the 2.31 unlocker tri color screen came up. 3)I flashed to NFSFAN's VZW 1.15, let customizations run, and 4)started to do the QPST AGPS fix. When I opened the first screen on QPST the only port showing was my phone (don't know why? I'm using VISTA) but I used that port. I did the QPST per instructions except I used the TELUS settings (posted just about everywhere). Per thermus' instructions, I did not do step 16; I manually changed the VZW registry settings that NFSFAN puts into HKLM/software/HTC/AGPS_SUPL to the TELUS settings and soft reset. It's been about a week and I still get GPS locks within 30 secs. The phone is super stable again. I had to dial *228 option 1 (I think that's it) to get data back, but that's all (no reauthentication). I'm not sure why some people are having issues? Might be hardware related?

Don't know if the instability was the result of flashing to 6.5 V4 but I have no urge to try 6.5 again. (but we all know that will change :))

Hopefully, this will help someone!

Good Luck and Happy Easter,

ST
[Touch CDMA Windows Mobile ROM Development] 151jcolon:
made(hard reset) now every is ok, thank a lot
[Touch CDMA Windows Mobile ROM Development] 151jcolon:
some app was the problem
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Great to hear - have fun LOL

And yet another reason for performing a hard reset directly after a flash - fixing issues before they become issues - might have to add that to my sig LOL

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] bolt-on:
Hey DD

I'm actually having a problem in the library window for HTC Audiomanger. I can't finger scroll.
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Me either, good thing there is a scroll bar along the right side of the list..

EDIT: actually scroll works but really crappy in the touch interface of it, but it does work just not in a usable way

EDIT #2: After checking a bit, it seems whats in the ROM is the latest available "HTC Audio Manager version 2.2 build 1822.3925" no newer versions found through my search

so unless there is a specific touch interface edit or fix for this, use the scroll bar or Media Player built into the ROM as well as the Media Player interface works just fine and sound/playback is good as well

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] chunnell:
I'm glad to hear of others having problems so that NSFAN won't think I'm inept. However, I don't think the problem is Verizon because when I had 6.1 I did have it working with Valhalla. If you are on 6.1 and have Valhalla, try these settings;

For Valhalla:

HKLM\Software\Valhalla Legends\GPSServer\Mode = 2

HKLM\Software\Valhalla Legends\GPSServer\PDEAddress = 5C8BC6D8

HKLM\Software\Valhalla Legends\GPSServer\PDEPort = 8889
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
The thing is, its not just this ROM, seems most custom ROMs especially 6.5 ones are having this issue and across several threads here at XDA and PPCGeeks there are alot of these "fixes" that work until you swap to a different custom ROM or into a WinMO 6.5, hell there are even people complaining of Stock ROMs having the issue and Valhalla NOT working for them regardless plus the port swapping method I posted earlier (that came off a PPCGeek thread for Vin and WhosDaMan ROMs)

The point isnt will it work, more will it work full time and not just for a while then get blocked out later

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] chunnell:
An interesting idea, and I tried it immediately. Unfortunately, nothing.
[Touch CDMA Windows Mobile ROM Development] chunnell:
Do you really think Verizon is actively trying to stop us from using this? That would make sense... Do you think they are reading these threads to find out ways to disable whatever settins we use?

Putin would be proud if that were the case.
[Touch CDMA Windows Mobile ROM Development] atoz350:
I think so...
[Touch CDMA Windows Mobile ROM Development] 350insp:
vzw has this sort of track record since the bluetooth was available on the phones. i'd rather be out of phone than use vzw. :)
[Touch CDMA Windows Mobile ROM Development] 350insp:
NFSFAN, Thanks for the 6.5 v6r2. It's been really stable with all my applications installed and heavy use.
[Touch CDMA Windows Mobile ROM Development] chunnell:
Just letting you know that I did a complete and utter reset of my phone in case Customizations from the Verizon ROM had locked me out permanently. http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS.

Then I ran http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix.

Then I ran NSFAN's GPS Cab and then I put in:

For HTC/SUPL AGPS:

HKLM\Software\HTC\SUPL AGPS\EnableAGPS = 1

HKLM\Software\HTC\SUPL AGPS\GPSMode = 4

HKLM\Software\HTC\SUPL AGPS\ServerIP = 216.198.139.92

HKLM\Software\HTC\SUPL AGPS\ServerPort = 8889

But it still didn't work. I had high hopes that I was just getting blocked out by previous Verizon customizations. But apparently it was all for naught.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Flash the 3.42.50 Radio, don't let customizations run. Flash back to my ROM, connect into QPST, and put in for IP: 66.174.95.132 and for Port: 8888. Save, and go into registry, put in the same values for ServerIP and ServerPort.

3.42.50 Radio
[Touch CDMA Windows Mobile ROM Development] chunnell:
Do I need to run the aGPS provisioning cab at the VerizonAGPSFix or do I still run just your GPS Registry Cab?
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Look Im no conspiracy theorist of any kind, I dont think there was a 3rd gunman aimed at kennedy, I dont think the moon landings were hollywood magic and I certainly dont wear tin foil undies LOL

I do think that Verizon would shut out aGPS/GPS to make an extra few bucks a month from the customers though, they have done it before and I wouldnt for a second hold it against them to do it again

I used to use Verizon a long time ago, had nothing but troubles and issues and the extras tacked on to every bill not to mention the constant billing errors that I would have to call 4 people half a dozen times each on my time be on hold forever on and on and on - I finally canceled my contract and then had to take them to court (and won) to get my money owed from all the overages and mistakes on the bills as well as the ETF returned to me

Luckily I document EVERYTHING and was able to prove my case and won

and Ive seen nothing but issues and additional fees from everyone I know that has ever used them in the past to present day

So do I think they read this forum.. personally I dont care if they do (many carriers do indeed read the various forums but little they can do)

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] chunnell:
"We're on a mission from God" Jake Elwood.

I will beat Verizon!!!!
[Touch CDMA Windows Mobile ROM Development] NotLutzik:
Been using sprint 1.12 for about 4-5 days. Zero problems and really nice rom. Thank you very much!!
[Touch CDMA Windows Mobile ROM Development] chunnell:
Doesn't work.

Radio installed w/o customizations

V6 V2 installed w/customizations

Tried GPS as-is didn't work. Rebooted.

Tried your settings didn't work. Rebooted.

Went back to original settings. Rebooted.

Ran your GPS cab file. Rebooted. Didn't work.

Put in your settings. Rebooted. Didn't work.

Changed Port to 8889. Rebooted. Didn't work.

REVISED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

216.198.139.92 port 8889

GPS Mode 4

Now it works!!!!!!!!!!!!!!!!!!!!!!!!!!!

I had tried these settings before, but the the complete reset that I did for having run customizations in the past along with the new Radio made the difference.
[Touch CDMA Windows Mobile ROM Development] chunnell:
Settings for Verizon aGPS. If you can't get yours to work, it is probably because you have run customizations with the upgraded 6.1 Verizon ROM. Because of this you must completely reset your phone. Unfortunately it isn't like reformating your drive. In order to reset the phone follow the following instructions...

http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS

Important! Do not let customizations run after initial boot up!! Take the battery out. When you reboot, it will not try to run again. The phone may try to customize after the second coke installation. Do not let it!!!!!

Install the new 6.5ROM on page 238. Now you can let customizations run.

Install the 3.42.50 Radio above in post #3817. Do NOT run customizations!!!

Reinstall 6.5ROM on page 238, again run customizations. It may be possible to install the 3.42.50 Radio without installing 6.5 V6 first, but that's the order I did it and it worked, and I'm not going to try it again just to see.

Go to http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix but install the GPS cab on page 238.

Install the MMS cab for the proper Data Connection settings, and do the rest of the instructions for the MMS cab on page 238. Reboot.

Edit the registry at HKLM/Software/HTC/SUPL_AGPS as follows

ServerIP: 216.198.139.92

ServerPort: 8889

GPS Mode: 4

Exit and reboot. Make sure the settings took after rebooting. Best to use the power button on top for rebooting otherwise data can be deleted after you change it.

Finally, GPS should work. It may take several minutes for initial lock.
[Touch CDMA Windows Mobile ROM Development] axemurderer:
Question:

Is GPS working for you as well as AGPS? Can you get a lock indoors, or do you have to be by the window or outdoors?

Thanks
[Touch CDMA Windows Mobile ROM Development] :
I've had a few issues with the most recent 6.5 v6 r2 rom. I've had to do the clear storage a few times. The issues I have are:

1. The contacts names will disappear and only numbers will show up in text messaging.

2. The phone hard reset when its battery died

3. And then a few other miscellaneous problems.

I'm about to sync it up again, but I was wondering if anyone knows a fix for this?
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
When battery dies you are prone to lose data. "A few miscellaneous problems", sorry but can't really help you there.
[Touch CDMA Windows Mobile ROM Development] :
kk, I've just never had it happen before so I was just curious, thanks!

What about the contacts and the numbers?
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Hmm... Do you have any applications that could interfere with the default MS Contacts app. Applications such as iContact?
[Touch CDMA Windows Mobile ROM Development] :
negative, the only apps i put on my phones is dashwire, smms, and the sprint gps file from you
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Weird :S Does it do the same thing after a hard-reset?

When you mention contacts names disappear, is this when you get incoming text or just when you enter a contact?
[Touch CDMA Windows Mobile ROM Development] :
It will be during the middle of a threaded convo, it happens on its own, randomly, they all switch over to just numbers, and the incoming texts start showing up as numbers. It happened almost instantly after I upgraded from v4 to v6r2, then i clear storage it....and it took a lil while longer the second time. Then my phone died, and kinda hard reset, because when it would load up it would run customization, but it would still have issues with dashwire and smms on start up, but when it would start it would freeze, but then I finally got it to clear storage again, and here we are again. I only put dashwire on...and so far so good with contacts, but I've haven't done any heavy texting yet
[Touch CDMA Windows Mobile ROM Development] the-wrangler:
been running v6r2 now since yesterday...ive been using it pretty hard...msn goin, texting, opera open etc and its way more stable..very little lagging at all. so far, so good. im writing this in opera with msn goin an im beeping with texts as i write..great job nfsfan. thanks mate.
[Touch CDMA Windows Mobile ROM Development] drdrewdown:
i've been using V6 on my sprint touch since friday morning. i've very pleased with stability & functionality. many props to NFSFAN for his hard work on all his stuff. prior to friday i was running sprint 1.12 which i luv'd but a co-worker & i were tempted by the 6.5 comments & so i took the leap.

shortly after flashing i was called into the field & was forced to use Garmin Mobile to figure out where i needed to go. It seemed like the voice prompts were much louder then i'd ever noticed & the phone worked great the whole way out there.

anyway just wanted to share my thoughts & experiences with this 6.5 rom, i think its a great piece of work, only have a few small beefs with it, but nothing i cant overcome.

still not having luck with adding custom words into the dictionary with the + sign being hidden. so i installed ezinput & it seems to work fine now just smaller keys. i've been using the crap out of it since friday & i'm very pleased. & btw for whatever reason my GPS works fine without installing the registry cab

GREAT work nfsfan
[Touch CDMA Windows Mobile ROM Development] tatnai:
I second that, strong as always. One comment:

Using quick menu's memory monitor, over the course of about a day, my available memory with no programs running drifts down from 57mb 5min after soft resent, to 44mb. Did a comparison of my running tasks just before a soft reset, and then 5 min after a soft reset, and there were three items taking up a lot more memory just prior to the soft reset then afterwards with all programs closed. This may be normal operation for these processes to accumulate a larger share of the RAM over time, but posting just in case this is not normal.

gwes.exe

after soft reset: 1.9mb

after 24h use: 4.5mb

filesys.exe

after soft reset: 2.3mb

after 24h use: 3.9mb

device.exe

after soft reset: 2.0mb

after 24h use: 3.4mb

Love your ROM, will try 6.5 eventually when I find myself bored.
[Touch CDMA Windows Mobile ROM Development] moonwoo:
Hey NFSFAN or anyone who may know the answer to some of these questions. I've just upgraded to your 1.12 sprint WM 6.1 ROM. First of all, I just want to thank you for this ROM. It's amazingly quick and efficient. Love the new Touchflo interface as well

just a few minor things I am thinking of here...

1. It seems like even after manually turning off activesync, it restarts up in the background memory. I tried turning it off again, but yet again it's there when I go check on task manager a few minutes later. tatnai, I know what you mean about the memory. Mine too also goes down to ~45mb. The phone is still extremely fast and efficient that I am not too worried about it.

2. EVDO radio seems to stay on even a few hours after I stop using the internet, so I just turn it off manually. If I leave it on, it does eventually shut off overnight. I dont know how much battery it will use up by leaving it on like that.

3. Will I lose data if I let the battery drain all the way like you said on WM6.5 as well?

4. Anyway to change the clock to the white background clock instead of the black background clock with white numbers on the home page? I love the black background one but it's sometimes hard to see with direct sunlight. (not a huge deal if it's not possible to do)

5. if I install 6.5 will there be any copyright issues? I know it's probably ok with 6.1 since I already had a Vogue phone with 6.1 on it. I just dont know how the copyright world is on the windows mobile products. If anyone knows just let me know. Just curious.

Again, just a few minor things that I was thinking of as I used the new WM6.1 1.12 Sprint rom. I love this forum and the new ROMs. I also want to thank NFSFAN and Detroit Doug once again. I'll keep browsing. Thanks again and have a good one!
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Ill try and answer to the best I can regarding these issues brought up

DO you synch your phone with your PC. if so I dont understand the issue, the memory footprint isnt large at all and doesnt affect anything, mine with just AS running is anywhere from 38 to 45, hardly an issue considering some ROMS run consistantly around the 42 to 50 range

Do you make/recieve calls in your phone, if you do its always going to have some sort of connection at whatever basic level, the EV or 1X indicator just means your connected to towers and wont be any more of a drain than you exert upon it (apps like games, word, data connections like IE, Opera, etc)

I really couldnt be sure, I dont understand how people let the battery drain to me its like letting your car run out of gas on the road in the city LOL

Extra batter, chargers (car, home, USB via PC) so Ive never let my battery die on me during use so I cant be sure

Im assuming your referring to within M2D? if so there are LOTS of clock themes out there just look around

By definition this WHOLE site as others is in some way a violation of copyright and patent infringments, but if your worried about the security forces of HTC and Microsoft storming your living space with tanks and the like, dont - they would shut down the forum looooong before Bill Gates in a Patton uniform is ordering snipers to shoot your phone out of your hand LOL

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] Raiden38:
Can someone confirm that Internet Sharing on WM6.5 works for BELL? Meaning that you can actually connect your laptop to your vogue and use your existing unlimited plan (no data plan)?

Thanks!
[Touch CDMA Windows Mobile ROM Development] EP2008:
I can confirm this is also happening with the 6.1 Bell 1.31 ROM.

Other's have also confirmed this and I believe it is the cause of the quick battery drain (which many people have also reported).

Using the advanced configuration utility, you can set it to disconnect the data connection every XXX minutes and that does the trick, but it should automatically do it (as it does in the OEM rom).

I'm guessing something just "broke" as I haven't seen this issue in the older NSFFAN roms.
[Touch CDMA Windows Mobile ROM Development] moonwoo:
Detroit Doug,

Thanks again for the helpful information. Yes I do activesync my phone with the PC. What I mean is, after I shut it down it seems to reload the program. So I just leave it alone. Yea it doesn't take too much memory so not too worried about it.

Didn't know that there were so many M2D themes' out there. Just found em!

Lastly I guess if it becomes a problem I can revert the phone back to the original HTC ROM.

Doug, you should setup a donation link. With all the help you give, I'm surprise you dont already have one!
[Touch CDMA Windows Mobile ROM Development] :
so dashwire threw a net cf compatibility error, and I took it off, and now my phone is mixing themes, and refusing to connect to the internet, it still texts and gets calls though
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Throw a few bucks to NFSFAN then .. I do this as a hobby and enjoy helping the community that gave me so much help and info in the past and as I dont really do all that much so toss some duckets to the Chef, he cooked it (insert starving artist commercial with the Sham-WOW guy (when he isnt beating up hookers that is)) LOL

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] moonwoo:
Just did. With all the work he does on making ROMs efficient, it's definitely worth a couple bucks (even though I am broke myself! haha). But yeah thanks again Doug catch you later!
[Touch CDMA Windows Mobile ROM Development] yandi3401:
I'm new at this of flashing, is there a tutorial I can use, or follow, to install the WM 6.5 ROM?

Thanks in advance!!! Really apreciate your work!
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Unlocking your phone is done via flashing it (bootloader mode of flashing)

1 -Download ImCokeMans 2.31 unlocker

HERE

Download ROM you want to use

6.1 M2D

or

6.5

Have the needed carrier cab for your carrier ready in case the ROM (search for "DCD Carrier Cab" in the search function to find the one for your carrier)

you choose is not carrier specific (most WinMO 6.5 ROMs)

If you need to upgrade your radio - minimum radio version of 3.42.30 for use with ROMs and GPS then get the newest ROM

HERE

2- Backup(PIM Backup) to save contacts, email, text or Synch with your PC to save contacts, mail

3- Extract RAR files into separate folders

4- Press and hold the power+camera+stylus in reset hole until tri-color screen comes up - it will say serial on screen

Plug into USB cable - it will change to USB on screen

5- On desktop folder double-click on RomUpdateUtility.exe

Follow directions on screen - Phone will reboot

6- go back into bootloader mode after restart (step 4) and connect for USB connection is verified on screen again

7- do the watusi.. this MUST be the watusi, the lindy and the charleston wont help and break dancing will corrupt your data BIG time...

8- Doubleclick on RomUpdateUtility.exe in the ROM folder you want to use

Follow directions on screen, phone will reboot

9- wipe hands on pants

10- go through setup and auto-run on screen then upon restart press and hold red button+green button+stylus in reset hole until gray screen appears

press the center button on D-Pad, wait, then press "end" (red) button when prompted (known as a hard reset as opposed to soft reset done with stylus in reset hole only)

11- Do the Watusi, if you dont know it learn it it will help you in the future (Oh and always have your towel handy)

12- go through setup and autorun, phone will restart, upon restart, power off, then back on

13- run carrier cab if needed

Detroit Doug