yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] soccerman821:
First off i cant wait for v 13.. and sorry for this post being a little off topic and geared towards verizon customers but, since the omnia just recieved a new verizon official rom that unlocked their gps.. wouldnt it be possible to find those exact settings and use it to have instant locks and not the bs we have now?

once again sorry for being off topic.. just thought there would be a big verizon group here
[Touch CDMA Windows Mobile ROM Development] austinite007:
I have the same device as you on Sprint. Where did you get the latest Bell radio from? Can you post a link? Thanks
[Touch CDMA Windows Mobile ROM Development] joe11211:
NOTE TO NFSFAN

there is a new google maps release v. 3.2 with layers! out today

hope u have time to include it in v13
[Touch CDMA Windows Mobile ROM Development] dmbpj:
I second this.
[Touch CDMA Windows Mobile ROM Development] incubus26jc:
i believe this is the rom that will upgrade your radio

http://www.htc.com/us/SupportDownload.aspx?p_id=70&cat=2&dl_id=98
[Touch CDMA Windows Mobile ROM Development] jmitr:
NFSFAN is on the Bell network as well (Lucky us!!). When he was releasing 6.1 ROMs which were carrier specific Bell's were always first.

The 6.5 ROMS are generic, however because NFSFAN is with Bell they work "out of the box" for us, no carrier cab needed. Here is a qoute from page 238:

For Bell, just flash the ROM as is, no provisioning or carrier cabs needed. P.s if you check my sig you'll see I have V12 as well.

This is NOT required. The Sprint radio is 3.42.30, the Bell radio is 3.42.50. Not much difference. If flashing the Bell radio, you will have a Bell splash screen at start up, etc. Back when the 6.1 updates were first coming out and not all carriers had one people were using other radios to get rev.a, GPS, etc. If your carrier has a 6.1 stock ROM with a 3.xx radio you do not need the Bell radio. The only possible exception is Verizon where letting customizations run may block you gps.

An end note for all the guys posting "can't wait for the next update......etc.......etc.....

While I'm sure NFSFAN appreciates the enthusiasm really coments like this just help make this thread reaaaaaaaalllllllllllyyyyyy Loooooooooong. We are at over 8,300 posts already, users searching for fixes can be frustrated by whole pages of anxious users with no information. NFSFAN's primary phone is now a TouchPro. He mentioned he is still working on his tp ROM. Lateley that has been the pattern, tp rom....Vogue rom....tp rom.... etc. Makes sense. Instead of posting how long you have been waiting maybe goto the Raphael CDMA thread and check if his latest TP Rom is out first. He posted that ROM today so chances are the Vogue ROM will follow soon. The longer he takes, the better it will be. Please be patient (I know, it's not easy:D). Personaly I can't wait to see if NFSFAN can get OpenGL working.....that would be huge.
[Touch CDMA Windows Mobile ROM Development] dealpapa1:
waiting for 23008 or 23009 :D
[Touch CDMA Windows Mobile ROM Development] tempests:
There is a sequence you have to do in order to get to that radio version.

1. Flash stock Sprint 6.1 Rom, letting customizations run radio 3.42.30

2. Flash stock Bell 6.1 Rom (don't let customizations run) radio 3.42.50

3. Flash custom .nbh to remove the blue Bell screen nbh file

4. Flash NFSFAN's Rom, letting customizations run

5. Flash NFSFAN's Rom, letting customizations run

6. Run Sprint Cab

7. Load contacts, backups and apps

8. Final Soft reset

All file links can be found in CodyBear's FAQ at:

http://xdaforums.com/showthread.php?p=3680840#post3680840
[Touch CDMA Windows Mobile ROM Development] tempests:
I beg to differ in opinion, with you. I found a big difference between my stock 3.42.30 radio and the Bell 3.42.50 Radio. At my office I could never get a bar, unless I went outside. Now with the Bell Radio installed, I get 2 bars inside and pegged outside.
[Touch CDMA Windows Mobile ROM Development] 1loudsvt:
going by nfsfans tp thread we will be getting build 23008 :-)
[Touch CDMA Windows Mobile ROM Development] ulricr:
I've tested the wired headset again today, and I can record from the microsoft in One Note, but the microphone doesn't work when I call someone (I use the Fav People shortcut)
[Touch CDMA Windows Mobile ROM Development] jurias:
.nbh

could some one direct me to #3 custom .nbh to remove the blue bell screen i cannt find it sorry.
[Touch CDMA Windows Mobile ROM Development] jmitr:
That's interesting. I know the Bell radio is awesome. I get great reception in my basement bathroom sitting on the tiolet (don't ask:D), and as far as GPS goes, 2-3 sats in the basement and a lock in 20-30 seconds (goes to 5-7 secs and more sats outside). I always use "my office" to test gps reception and "bars" after a new ROM flash even though the ROM itself should have nothing to do with that.

Shouldn't make a difference, but I tested mine using M2D (have I ever mentioned not being a fan of Titanium?). I call people from the "people tab" of Manila. I will test it with Titanium tomorrow and report back. Could be one of those ghost flashing issues your having that will dissapear when you upgrade to V13.
[Touch CDMA Windows Mobile ROM Development] jamezelle:
most custom cooks will replace the spash screen to remove the default. i dont think he is referring to a specific rom.
[Touch CDMA Windows Mobile ROM Development] juddy:
I just went through this process and the Bell splash is still there.
[Touch CDMA Windows Mobile ROM Development] br125:
This is the HTC bootsplash, it will replace the Bell screen.

You should be able to just replace the ruu.signed.nbh file in the folder

you have NFSFAN's rom saved to and run the rom update utility, or flash

it from the memory card if I'm not mistaken.

Also, I tested reception with both my verizon 3.37.38 radio and the "upgraded" Bell radio 3.42.50 and I must say it was NOT an

upgrade for me personally.

VZW radio = better reception for me, so try it out and don't just rely on

a higher number to be better...
[Touch CDMA Windows Mobile ROM Development] juddy:
Thanks for the splash, the FAQ states it could make things worse.

Note on Radio Upgrading By Doug:

"An upgrade is not needed - it can help depending on your carrier,

but its based on a carrier by carrier exceptions.

I'm on Sprint with the 3.42.30 radio with no issues whatsoever

where upgrading to 3.42.50 on some carriers can create problems."
[Touch CDMA Windows Mobile ROM Development] PatcheZ:
How do i change the font in google maps?

before updating my google maps, the font was originally bigger with clear type ... but after the update, it's small and barely legible.
[Touch CDMA Windows Mobile ROM Development] tempests:
What I found the difference to be, between my Sprint Radio and the Bell 3.42.50 radio, was call reception was way better, dropped calls are gone and the volume is louder. I now have to turn my volume down, on both the phone and MOTO S9HD headset. Also, whether the Bell radio is the reason or not, my bluetooth reception went from 15 to 20 feet, to over 35 feet, and no drops, flutters or static, when going to another adjacent room. GPS also syncs up faster. Lastly, battery life is better. This may be because the radio is more efficient?

Users with different carriers may have different results, so I suggest testing it to see which radio works better for you.
[Touch CDMA Windows Mobile ROM Development] tempests:
That is one person's opinion, or like we all use here, "a disclamer". The radio upgrade was better for me.

I have seen paople here say the new ROMS and/or radio upgrades, bricked their phones. But you will never know for sure, until you try it.

My suggestion always is:

To be safe, stay with your stock ROM and radio. But if you are hoping for more, and are willing to trust some single programmer's ability, to offer a better custom ROM, with more features and better quality, then by all means, use NFSFAN's custom ROMS and a newer radio. For me, if it is new, I have to at least try it. I can always flash back and start over. After all, there is only time involved.

As one famous actor said:

"If you want to taste the fruit, you must go out on the limb"
[Touch CDMA Windows Mobile ROM Development] ianPhillips1:
Strange Inbox Issue

Lots of searching and now my eyes are bleeding......

I am running v12 on VZW and it is nothing short of great!! THX NFSFAN!!!

I followed all of the instructions on Codybears FAQ flashing the phone 3 times before digging in for round two. Everything works perfect including GPS!! Here is my issue: When my inbox syncs (set at 5 min intervals) it pops up every time and is really starting to drive me nuts. If anyone is having this issue please chime in as I believe I am the first. It is a small detail in an otherwise perfect ROM that gives me great battery life after going back to my stock batt when my sedio died. Any and all input would be great.

Ian
[Touch CDMA Windows Mobile ROM Development] snowcraig:
So, should I pull the trigger on v12, or wait for v13?
[Touch CDMA Windows Mobile ROM Development] ianPhillips1:
It will be better than what you are running currently!!
[Touch CDMA Windows Mobile ROM Development] :
You could wait a day or to until v13 to come out. That would be what I would do.
[Touch CDMA Windows Mobile ROM Development] blauze:
That's what i said to myself last week... can't wait...

On another subject, I'm trying to connect to my device through data plan network like i do while connected on wifi. It seems ports are blocked. Anyone one have an idea how to work around this issue?
[Touch CDMA Windows Mobile ROM Development] WOOPTIEWOOUS:
cab it maby

ok so you are on same network as i with sprint , are you able to cab it all up.so as to share it , im like the fact you are getting those results
[Touch CDMA Windows Mobile ROM Development] snowcraig:
I am already running v10. My GPS is not currently working though, I am hoping reflashing will fix it.
[Touch CDMA Windows Mobile ROM Development] tempests:
There is no way for me to cab it up. You have to follow the instructions that have been posted in the FAQ and all over this thread.

I have 100% success with the following fool proof install process.

Download all the necessary files.Then:

1. Flash stock Sprint 6.1 Rom, letting customizations run radio 3.42.30

2. * Flash stock Bell 6.1 Rom (don't let customizations run) radio 3.42.50

3. * Flash custom .nbh to remove the blue Bell screen nbh file

4. Flash NFSFAN's Rom, letting customizations run

5. Flash NFSFAN's Rom, letting customizations run

6. Flash NFSFAN's Rom, letting customizations run

7. Run Sprint Cab

8. Load contacts, backups and apps

9. Final Soft reset

* You can leave out 2 and 3, if you don't care about upgrading the radio.
[Touch CDMA Windows Mobile ROM Development] cointelbro:
does anyone know what the deal with the time on the lock screen being cut off slightly at the bottom is? it's been like that in every build of 6.5 i've used except for 23001, then the bug came back in 23004. does 23008 fix this or should i just use S2U2?
[Touch CDMA Windows Mobile ROM Development] calisoldier83:
I never had this problem with any 6.5 version have you updated s2u2 a new version came out recently.
[Touch CDMA Windows Mobile ROM Development] ppcgeek:
GPS DOESN'T WORK SINCE MULTIPLE FLASHES of NFSFAN 6.5

Has anyone answered this? I have reflashed five or six times and still cannot get the GPS to work. That is my ONLY problem, which is truly a problem for an otherwise excellent ROM.
[Touch CDMA Windows Mobile ROM Development] Duuuude:
It's there and you probably didn't notice. It's cut off by about 1 row of pixels. Very subtle. No biggie for me.
[Touch CDMA Windows Mobile ROM Development] tempests:
I've never had the problem in any build either. My lock screen always looks fine.
[Touch CDMA Windows Mobile ROM Development] tempests:
There are no missing pixels on my screen. I have about 1/8th to 3/16th of an inch, of dark background, below the time and long date. Maybe there is a difference with different versions of the phone carrier. Or maybe some third party install is making the status bar at the top bigger. But there is absolutely no cutoff here.
[Touch CDMA Windows Mobile ROM Development] Duuuude:
Sorry, I meant just the clock in the unlock screen. Just the font iteself is cut off a bit. I think it has been around for at least the past few builds.
[Touch CDMA Windows Mobile ROM Development] neuteboomt:
I kind of like the lower part of the clock missing on the lock screen. It is something diffrent.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
The new dialer you guys tried before here does have a problem. It always dials the last dialed number if you press the green hard button to open the dialer. If I can't fix it, I will revert back to the normal one.

Now I'm deciding what build to use.... 23009 or 21928. Probably will go with 21928, since I have 23008 running on my Touch Pro and its not as good as 23001.
[Touch CDMA Windows Mobile ROM Development] cointelbro:
23008 is worse than 23001?

these build numbers make no sense

if you have time, can you give us a breakdown of what the different builds are?

also, when you say normal one, do you mean the current dialer that has the ghosting bug, or the CDMA dialer?

i would love to go back to the cdma dialer myself... there seems to be a slight delay in picking up my voice with the GSM dialer that wasn't there in v11
[Touch CDMA Windows Mobile ROM Development] 4thought:
I'm using it and I noticed that sometimes it does not dial out in this situation. I've never really zeroed in on the conditions leading to dialing or not though.
[Touch CDMA Windows Mobile ROM Development] rarahpb:
I have been using it too n it hasn't been up to par so I switched back to NFSFAN v12 dialer.

Hey cointelbro

If you google search about build numbers (referring to the comment about 23008 being worse than 23001) and you will get a better understanding on it.
[Touch CDMA Windows Mobile ROM Development] Duuuude:
Sorry, I meant just the clock in the unlock screen. Just the font itself is cut off a bit. I think it has been around for at least the past few builds.
[Touch CDMA Windows Mobile ROM Development] koman90:
Agreed, the new dialer is buggy!

I agree with you the new dialer is buggy. I can't re-create the problem that NFSFAN is talking about with the green "send" hardkey, but when i awnser a call not only is there a delay in the call awnsering, bit i have heard noises, ontime it was a beep so loud it startled me and i droped my phone :eek:. We defently need to revert to the old dialer, and when we say old dialer the las version of your rom i used was v9. and also has anyone noticed that the dialer in v12 cannot make 911 emergency calls?! I believe this should become part of the standard testing process, as i gort in a situation today where i was a hair shy of calling the police, long story, and my phone kept locking up every time i would type 911. Other than the dialer app v12 was perfect great job NFSFAN!

Also as a request to v13 can we get the new i think it was called EZ input keyboard mentioned previously.

See quotes below including quotes of quotes.
[Touch CDMA Windows Mobile ROM Development] johndoe1980:
"Roaming ONly" option not present in V12

Can someone confirm this ?
[Touch CDMA Windows Mobile ROM Development] bobzero:
I agree with the move back to the CDMA dialer. I had to revert back to v11 because I couldn't stand the glitches and oddities from the new dialer. Plus this way we'll get the data arrows working again. Good call NFSFAN.
[Touch CDMA Windows Mobile ROM Development] tempests:
That is EXACTLY what I am referring to, the clock on the unlock screen. I don't have missing pixels, unless there is something below the time and long date that is suppose to be showing.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
grrrr... I'm going back to 23001. That is the last build I used that had no issues.
[Touch CDMA Windows Mobile ROM Development] joe11211:
Thats the case
[Touch CDMA Windows Mobile ROM Development] 1loudsvt:
have you done the agps hack that is in the wiki? If so redo it using the telus server settings. also apply the same settings to the registry and it should work i get locks indoors in less than 20sec. the info can be found in the vogue upgrading etc forum and the wiki.
[Touch CDMA Windows Mobile ROM Development] 1loudsvt:
21928 has all the finger friendly stuff though :(
[Touch CDMA Windows Mobile ROM Development] cointelbro:
23001 probably has the same functionality. you can still finger swipe to move from tab to tab

but yeah, especially in light of the 911 bug, PLEASE revert to the CDMA dialer. i and hopefully everyone else here wouldn't want to be caught in a situation where i needed to call for help and couldn't. that little bug could easily be a disaster in the making.

are there no other fancy dialers that could be used? really, the only thing i'd miss from the GSM dialer is the slide to answer functionality, and surely there's a non-dialer way to do this, i think the S2U2 guy makes one
[Touch CDMA Windows Mobile ROM Development] cointelbro:
just tried 911 myself, it locks the phone app up and you have to soft-reset
[Touch CDMA Windows Mobile ROM Development] lotherius:
Certainly appreciate all the testing - I had problems on some older builds with freezing up on incoming calls, couldn't answer, etc. None of those problems on v12, though I haven't tried 911. I'd rather stick with v12 a bit longer than get a buggy v13!

As far as the dialer.... it's not like I talk on my phone much, and when I do, I don't dial, I go through various photo-shortcuts :)..
[Touch CDMA Windows Mobile ROM Development] koman90:
Builds 219xx i think are sill development\experimental bulids and may or may not catch on, any way i already think WinMo 6.5 is "finger Friendly" compared to WinMo 6.1

That's What i do in my spare time i'm a public beta tester. I always wished i cloud program but i stink at learning programming languages, i never made it past the "Hello world, what is your name?" program, So i contribute to the software community the only way i know how, to test and provide feedback on software that is under development.'

Sorry NFSFAN but for safety reasons i'm going back to v9, because it's the last version i have a backup copy of, Unless someone can send me a link to v11.
[Touch CDMA Windows Mobile ROM Development] Snakehn:
this new dialer that just came out is almost perfect, it takes over the slide to answer from winmo when is locked, so if we could only fix that bug of dialing the last number when the hard button is pressed, and that would be Gold!
[Touch CDMA Windows Mobile ROM Development] 1loudsvt:
yes 6.5 is much better but 21928 is awesome...21xxx builds are ui experimental only so the core functions are the same or close to the current builds.
[Touch CDMA Windows Mobile ROM Development] tempests:
V12 is more stable than 9 through 11. For safety reasons you should be using V12. But you know that already, because you are a public beta tester.:rolleyes:
[Touch CDMA Windows Mobile ROM Development] WOOPTIEWOOUS:
the point to upgrade

1. Flash stock Sprint 6.1 Rom, letting customizations run radio 3.42.30

2. * Flash stock Bell 6.1 Rom (don't let customizations run) radio 3.42.50

3. * Flash custom .nbh to remove the blue Bell screen nbh file

4. Flash NFSFAN's Rom, letting customizations run

5. Flash NFSFAN's Rom, letting customizations run

6. Flash NFSFAN's Rom, letting customizations run

7. Run Sprint Cab

8. Load contacts, backups and apps

9. Final Soft reset

* You can leave out 2 and 3

thats the point to upto the bell radio . so you can just cab up the radio to install ? sence thats what is the end result ..or must it be done thou the upgrade procedure...
[Touch CDMA Windows Mobile ROM Development] tempests:
It must be done through the upgrade procedure.

When you flash with the Bell Rom, to get the 3.42.50 radio, you are actually flashing your phone for the Bell system. The radio is in the Bell ROM. So you have to follow the process after flashing, using the Bell Rom.
[Touch CDMA Windows Mobile ROM Development] emphanidzo:
GPS Not Working

Ok, Im new to this. I have a new unactivated Verizon Touch. I have tried alot of things. Nothing has worked. Finally I updated the radio to 3.42.50 with no customizations. Then I flashed NFSFANS v12 Rom and the verizon cab withit. Ive made sure that location is on. I cannot find any satelites. when i run the htc gps tool i can vew $GPGSV,1,1,00*79 $GPVTG,,T,,M,,N,,K*4E and so on, but no fix and no satelites. can anyone help me.
[Touch CDMA Windows Mobile ROM Development] Snakehn:
and before you updated the radio, did you happen to notice which version of the verizon ROM were you running? because if it came with 6.1, you are screwed and have lot of homework to do to get GPS fixed
[Touch CDMA Windows Mobile ROM Development] emphanidzo:
No im not sure, I looked at it, but i honestly dont remember. it came with wm6.1 radio 3.37.78. ????? Why is this a problem?
[Touch CDMA Windows Mobile ROM Development] koman90:
Resonce to tempests's comment on the 911 Bug

Let Me Express my Opinon About your Comment as quoted above,

If you read my previos post or even the quote in that post you'd notice that v12 can't dial 9-1-1, the universal SOS/emergecy phone number for the united states, for that verry same reason i'd recommend any person using v12 in a country wher the SOS phone number is 911 to flash back down to an older version with the original CDMA dialer, Please read the entire conversation including quotes of quotes if you're going to comment on somting :mad: especaly if your going to make a person who has ben working with computers for 10 years of his 19 year old life look like he was born yesterday. :p

As I was Saying This 911 bug is a Huge Saftey Issue, i'd recommend anyone using v12 in an area where the SOS phone number is 911 and not 999 either a) flash back to an older versin while wating for v13 or b) upgrade to v13 As soon as posible.
[Touch CDMA Windows Mobile ROM Development] WOOPTIEWOOUS:
maby not cab but ruu

RUUs that update the radio only.. do exsist and can be done with out the full process .. I asked one that has made some for assitance in the ruu radio update only .. i need a tutorial on how to make them... for the vogue
[Touch CDMA Windows Mobile ROM Development] koman90:
Posible Solution for emphanidzo

Mine Is 3.37.78 But that came through after i ran a PRL update on WinMo 6.5, if i recall correctly the stock radio version was 1.50.xx , This tells me that you do have the latest raido vesion however, your account migh not have activated properly because of the instant skip to 6.5, the vouge's sock rom through verizon dose not support gps capiblity except for E911 use, as do all of verizon's phones even the free ones, you may need do incremental upgrades as i did when i decided to start using 6.5 as shown below

Stock Rom Windows Mobile 6.0

Vreizon Updated Rom Windows Mobile 6.1

NFSFAN's Custom Rom Windows Mobile 6.5

In betwene incremental "upgrades" you will need to:

Re-Activate Your Phone by dialing *ACT (*228)

Preform A PRL Update or as verizon calls it "Update Your Roaming Capibilites"

You will aso want to make shure your data connection to the following

Dail:

#777

Username

yourtendigitnumber@vzw3g.com

Password:

vzw

Hope this helps if you have any probles or you need links to the roms just send me a message
[Touch CDMA Windows Mobile ROM Development] emphanidzo:
to the above poster. It sounds like you have your vogue running well. Is the gps working on it. As i stated, im running 3.42.50 radio with v12 rom. can you perhaps give me a better guide to reflash this to get it to work?
[Touch CDMA Windows Mobile ROM Development] nopick:
I am running V12 and installed http://www.4shared.com/file/117191822/66480ee4/Shekhar_phone_canvas.html. It has been working flawlessly and will dial 911. Green hard key just launches the dialer. My Touch is an Alltel model if that helps.