yashsingh1/xdaforums huggingface dataset:
[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 pos 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 borne yesterday. :p

As I was Saying This 911 bug is a Huge Saftey Issue, i'd recommend anyone using v12 in an are where the SOS phone number is 911 and not 999 either a) flash back to an oldr versin while wating for v13 or upgrade to v13 As soon as posible.
[Touch CDMA Windows Mobile ROM Development] koman90:
Yeah But there are several factor's you missed

You have Sprint, No verizon, Posible Network Conflict?

You have Raido 3.42.78 notn 3.37.78

I had not hacked my rgistry, or installed third party software as it hapened whe i hard reset my phone.

Other confirmed cases of this "Bug" have occured with other verizon users. as shown below

Please man get your fats straight
[Touch CDMA Windows Mobile ROM Development] tempests:
Yes my GPS works perfectly. I have installed TomTom software on my microSD card and it works flawlessly. Google maps and Microsoft Bing both use the GPS perfectly.

Please let me what carrier you are with and I'll see if I can point you in the right direction. Also read CodyBear's FAQ. It is put together very well and there are many answers to most problems reported.
[Touch CDMA Windows Mobile ROM Development] tempests:
You just said it! "Verizon", which means it is a carrier specific incident. Also to correct you, I have Bell's 3.42.50 radio installed, not 3.42.78. :rolleyes:

There very well may be a problem with your radio version. Also, I have not hacked my registry. Another reason may be, Verizon's version of the Vogue has some mods done to it, that causes problems with 3rd party ROMS. (I'm guessing on that).

There are many Verizon users that are not having problems.

It is pretty clear you didn't follow the proper procedure when flashing your phone, because I see you have given bad flashing advice 2 times. I suggest you read Cody's FAQ from top to bottom. Then you will have the proper education for this and have your facts straight.

For a college student, you sure have a lot of mis-spellings.;)
[Touch CDMA Windows Mobile ROM Development] blauze:
It's cute but it's slow, I agree. But I do like that big fat red End Call! It sometimes release a lot of pressure after a painful call... :)

And Google Map with Layers rocks.

Who's for a poll to cancel V13? Go straigth v14! I think this one is cursed.
[Touch CDMA Windows Mobile ROM Development] jmitr:
Way back when NFSFAN first opted for the gsm s2a dialer in his 6.1 ROMS I also called 911 to test it out. It worked. It also works for me with V12 on the Bell network.

I wrote the dialer FAQ in CodyBear's 6.5 FAQ. Alot of the information and wording I supplied I got from NFSFAN himself. I also have tested everthing prior to writing about it.

Similiar to Tempests I leave my ROM uncustomized for the first 3 days after flashing. The ONLY thing I do is activate my email exchange which automatically reinstalls my contacts. I do not even do a pim restore untill I am done testing.

If you read back thru this thread you'll find a post from me where I purposly flashed the ROM only once, from active sync no less!!! and was able to recreate almost every little snag people were reporting. I then followed my usual flashing procedure and all the problems cleared up. NFSFAN himself recommends flashing from bootloader, then hard resetting. On another forum he recommended to a few users experiencing wierd issues to flash back to stock first then custom. The current procedure in Cody's FAQ (written by Detroit Doug) is the result of trial and error to see what worked the best everytime.

I'm not sure if an improper flashing procedure could have led to your not being able to call 911. If more Verizon users test this out and report back we may indeed find it is a carrier problem with the gsm dialer.

As stated, tested working on Bell.
[Touch CDMA Windows Mobile ROM Development] story:
Take your time making the ROM man!

Thanks for your hard work.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
You guys will like what I've done for v13. I made a hybrid 21926 XIP + 23001 SYS (23008 Voice Command & 23009 Office). This will be replicated on the Vogue once I'm finished with the Touch Pro. Expect an update this week for v13.
[Touch CDMA Windows Mobile ROM Development] joe11211:
i m on sprint and get the same 911 freeze, the dialer freezes not the phone.
[Touch CDMA Windows Mobile ROM Development] blaudick:
Sounds great NFS

I want to encourage everyone to donate at least a 20 spot to NFSFAN for all his hard work. If he has had made your life less aggravating everyday by making your main communication device work better then that's the least we can do.
[Touch CDMA Windows Mobile ROM Development] extraghost:
I have a question about the end key in the Verizon 1.15 rom. Before on the previous rom i used the end key would go back to the home screen from where ever I was including IGO8. In this one the end key seems to only go back to the touch flo screen. Before it would go back to the main clock screen after pressing it twice.

Thanks
[Touch CDMA Windows Mobile ROM Development] cointelbro:
wow, how'd you do that? O_o

will this fix the voice command memory crash? if i start the phone up with TouchFLO, the voice command crashes due to low memory as soon as i start operating the phone

doesn't seem to be happening with titanium though
[Touch CDMA Windows Mobile ROM Development] cointelbro:
as far as the 911 thing goes, mine locks up too, and i've followed the correct 3x flashing procedure after i had it explained to me, so i know it's not my fault

right now, i have no custom apps installed on my phone (other than a few games on my SD card), so it's not that either

it's probably something carrier/radio specific, or it may even have something to do with different batches of parts that make up the phone's hardware, but that's a moot point because if it doesn't work 100% of the time for everybody it's not acceptable.

911 is a VERY BIG DEAL and HAS TO WORK. now i'm sure NFSFAN has gotten this worked out for the next version of his rom, but in the meantime, don't fly off the handle at people reporting a serious bug just because you don't have it.

NFSFAN: would you consider releasing a CDMA dialer and a GSM dialer version of v13, so that if some testers report the 911 bug again, we can still get all the other features?
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
****UPDATE****

ChangeLog v13:

ETA: July 24-25th

*New Helvetica OTS font

*Updated HTCUSBToPCPopUp -- 2.2.1914.3124

*Updated MP3Trimmer -- 1.2.1914.2726

*Updated LongPressEndKey -- 1.2.1914.3227

*Updated MHubVO -- 1.75.090515_X0 -->Custom

*Updated StreamingSrcFilter -- 2.7.1914.3024

*Updated RSSHub -- 2.1.1.1093

*Updated Bluetooth Explorer -- 1.2.37656.91

*Updated ResourceProxy -- 1.0.1915.1630.00

*Updated TouchFLO -- 3_0_19143222_RH00

*Updated Youtube -- 1.6.1916.1426

*Optimized DShow package

*Rolled back to CDMA Canvas (stable and works properly)

*Fast download/high quality setting now available in Youtube

*Proper volume control in YouTube

*Touch Response disabled by default

*Fixed WMP Memory leak

*Optimized touch panel

*Optimized ROM (speed & auto cache)

*Tap and hold X to close disabled

*Updated Google Maps -- 3.2

*Updated Bluetooth Setting -- 2.11.1.0

*Updated BTBPP -- 1.9.3.0

*Updated CommManager -- 2.9.1.0

*Updated Concurrence Manager -- 1.5.1914.2726

*Updated DRMMiddleWare -- 1.5.1914.2824

*Updated HTC Animation -- 1.3.5.0

*Updated HTC Scroll -- 2.0.1915.3028

*Updated HTC BT Settings -- 1.4.2.0

*Updated Picture Enhancement -- 1.50.1914.2727

*Updated PowerOff Warning -- 2.9.0.0

*Updated SharedModules -- 1.01.1914.2728

*Updated SMSInboxThreading -- 1.35.0.0

*New Icons (Device Info, Camera, MP3Trimmer)

TODO:

*Fix gray backgrounds in dialog boxes (all themes)

*Modify NFS Modern theme

*Build OS Hybrid 21926 XIP & 23001 SYS (23008 VoiceCommand, 23009 Office)
[Touch CDMA Windows Mobile ROM Development] cointelbro:
that sounds awesome!

is there any to add finger touch scrolling in the HTC audio manager? that's the only thing keeping it from perfection. i'm guessing that that's just something that HTC will have to take care of though. it's odd that it's the only decent audio player on the WM platform.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Media Player does fine for me :)
[Touch CDMA Windows Mobile ROM Development] cointelbro:
blech, i can't stand the + sign interface, it's not touch friendly, and for some reason, mine can't search beyond 999 songs, which is hardly enough to fill an 8GB microSDHC
[Touch CDMA Windows Mobile ROM Development] tempests:
Then I suggest reading the FAQ and re-flashing from scratch. Start by flashing back to stock.

One question though:

Did you upgrade your radio? I'm on Sprint and upgraded to the Bell 3.42.50 radio. I can call 911 just fine. We may be onto something if you have not upgraded.

No one is flying off the handle. We are trying to help. There is a logical reason why some have no problems and others do. But to call something a bug and blame it on the ROM, when all the facts are not in, is just causing confusion. There are a lot of factors to consider.

Here are a few:

Was your ROM and/or Carrier file download contaminated; Did you miss a step when flashing; Did you flash using a bootloader or flash off the SD card or AS; What radio are you using; Did you install any programs or make any mods; Was your phone malfunctioning before you upgraded.
[Touch CDMA Windows Mobile ROM Development] tempests:
What carrier are you with and what radio version are you using?

If everyone, who are having problems or reporting bug, would tell us your carrier, Rom version and radio version, it would help a lot.
[Touch CDMA Windows Mobile ROM Development] cointelbro:
NFSFAN's v12, Verizon, 3.42.50 radio

phone app freezes on 911

not that this matters since we're going back to my beloved CDMA dialer
[Touch CDMA Windows Mobile ROM Development] tempests:
I'm bugged because some are having a 911 problem and others, like me, are not. We know it's a Verizon phone problem, because more Verizon users have reported the problem. I'm with Sprint and I don't have the problem, but someone on Sprint just reported they do. However, we don't know their radio version. So it may very well be carrier and radio specific or a BAD install.

It does matter. If we all thought like that, there would be so many bugs reported, we couldn't keep up. You are not the only person that matters here.;) The majority of people are not having any dialer problems. And the majority voted for the dialer we have now, which is way more sophisticated.

The CDMA dialer is so last year.;)
[Touch CDMA Windows Mobile ROM Development] Snakehn:
some vogues come with 6.0, some others come with 6.1, verizon blocks the gps in 6.1 so that it ONLY works with their navi software.

search around the forum for a fix.

now... looking forward to try this new V13 ROM ;)
[Touch CDMA Windows Mobile ROM Development] joe11211:
Carrier: Sprint

Device: Touch Vogue

Radio: 3.42.50

ROM: NFSFAN 6.5V12

Issues: 911

but i still want the curent dialer, the old one is terriable, and has a lag when phone buttons are pressed.

BTW why is it called GSM and CDMA? isnt it just the default oem dialer vs. a newer htc customized dialer?
[Touch CDMA Windows Mobile ROM Development] tempests:
I would guess your 911 problem may be the way the install went or some specific software or registry mod? If we are both on Sprint and I'm not experiencing the same 911 problem, then we may be getting closer to the root of the problem.

Maybe I'm configured differently. The only thing I always do after flashing to the latest ROM, is go into my phone settings and set up my username and password and domain name again. Because after the flash, that info is blank and I cannot send email or text messages, until I put the info back in.
[Touch CDMA Windows Mobile ROM Development] blauze:
you're the best! thanks again for all your hard work, I really appreciate it.
[Touch CDMA Windows Mobile ROM Development] cointelbro:
ok well i hope i never run in to you somewhere and need to call for help :p
[Touch CDMA Windows Mobile ROM Development] blauze:
One thing that would be really great is to add the registry key for file association with .wgt and .widget. Can you make that too? I believe one of the next builds will integrate it later on. Marketplace is starting July 27th.

[HKEY_CLASSES_ROOT\.widget]
@="riapp"
"Content Type"="application/x-wm-widgets"
[HKEY_CLASSES_ROOT\MIME\Database\Content Type\application/x-wm-widgets]
"Extension"=".widget"
[HKEY_CLASSES_ROOT\.wgt]
@="riapp"
"Content Type"="application/widget"
[HKEY_CLASSES_ROOT\MIME\Database\Content Type\application/widget]
"Extension"=".wgt"
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
The problem with 911 is as follows... There is no such thing as verizon users have this issue and others don't. Check your registry settings for the DialParser being used. If its phonecanvas.dll your 911 will not work. If its ddcall.dll your 911 will work. Simple.
[Touch CDMA Windows Mobile ROM Development] cointelbro:
how are people's dll settings different with the same version of the ROM :confused:
[Touch CDMA Windows Mobile ROM Development] Wooglin:
I cannot Dial 911 either... and I found it out the hard way.

I got in a car accident this morning. There weren't any injuries, and luckily the other person involved had a working phone... but this needs to be fixed in case the next guy with this ROM isn't as lucky...

Here's my info...

Carrier:Verizon

ROM: NFSFAN's v12

ROM Date:06/28/2009

Radio:3.37.48

Custom Software: None

Flashed 3x yesterday, only synced to Exchange for contacts.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Others installed other dialers.
[Touch CDMA Windows Mobile ROM Development] joe11211:
I have the issue, and I have not installed any dialer, I got the default v12 dialer.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
I'm talking about those who say 911 is fine.

Anyhow going back to CDMA dialer means no more finger friendly volume either :'(
[Touch CDMA Windows Mobile ROM Development] cointelbro:
really? why?
[Touch CDMA Windows Mobile ROM Development] cointelbro:
wouldn't it be possible to use the shekar phone canvas and just create a tiny background app that opens the phone app when the green button is pressed in the same manner as a softkey instead of the hardware function? when in tFLO, if you press the phone softkey, the dialer never autodials the last call
[Touch CDMA Windows Mobile ROM Development] Jacklad:
"Bluetooth Disconnected" notification, headset mic not working

is there anyway to disable this message from popping up whenever bluetooth is disconnected?

Also, I've read a few references to wired headset mics not working on V12 - I recently purchased a stereo headset which plugs directly into the Vogue without using an adapter (use it for listening to Sirius while driving) , and the mic doesn't work - I thought it was the cheap headset, but now I'm not sure....
[Touch CDMA Windows Mobile ROM Development] koman90:
Thak You, NFSFAN!

Thak you NFSFAN for providing a solution to my problem. I was Realy upset last night because of pepole acusing me of trying to make you put the old dialer back in, when honestly i hate the old dialer :mad:. And What Really Upsets me is i know ahat i'm talking abut and pepole treat me like a n00b. :(. I Hope You Keep the GSM dialer, i just hope these registry issues can be fixed and it becomes a little more compatible with may call firewall app to block unwanted callers. I flashed back up to v12 today and aplied the registry patch as perviously mentioned and it worked. Thank You So much.

I am looking forward to v13, very much I hope it is just as good as all the others with minimal "bugs". :D
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Sure, but is it worth my time? I'm doing all this practically for free you know.
[Touch CDMA Windows Mobile ROM Development] cointelbro:
i'd donate but i'm literally living hand to mouth right now

isn't there already an app out there that basically does what i'm saying? AEButton Plus maybe?
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Do a search on this thread. Don't ask the same question that has been answered at least 10 times.
[Touch CDMA Windows Mobile ROM Development] Prowess:
Bell Users for V13 Dialer WORKS

Look at the poll results NFS, the new dialer has won? Those whose dialers that freeze, this happens to me too!

However is you leave it for about 30 seconds, it eventually dials and works! I've tested and ended the call, they called me back and I was explaining the situation as 'it was a test'. They understood.

For all those whose dialer freezes, let it untouched for a while and EVENTUALLY IT DIALS! The new dialer has NO PROBLEMS.

Everyone clear?

Regards,

Bun
[Touch CDMA Windows Mobile ROM Development] Berzerk54:
Flashing inconsistencies, remnant files not overwritten probably. Hence the need to flash multiple times for each ROM so there are no bread crumbs from the previous ROM left behind.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
The dialer was never made for this phone. Firstly its a GSM dialer. Secondly I've yet to find out which device it is from. It is not the Tachi Dialer, it is definately a QVGA dialer, that was not ported from VGA. The green send key does one thing... opens the dialer. This dialer is programmed to dial the last call upon pressing the send key.
[Touch CDMA Windows Mobile ROM Development] jstn76rs:
I think that the dials poll was skewed a little bit. Some voter might have voted gsm dialer because it worked perfectly with the 6.1 roms and voted right away before even trying it out on 6.5. Myself thought there were going to be updates for the 6.1 so i voted gsm but would change to cdma now that i've changed over to 6.5.
[Touch CDMA Windows Mobile ROM Development] tempests:
And why is that? ;)
[Touch CDMA Windows Mobile ROM Development] Barogi44:
Is there anyway to get the qwerty keyboard that originally came on the bell's touch, the one with 2 letters per button?
[Touch CDMA Windows Mobile ROM Development] tempests:
Well here you go::eek:

I only install your Rom and never install any other dialers or existing programs. The only thing I do is add back my username, password and sprintpcs.com domain name for test, email, etc.

I was hoping to figure it out because the V12 dialer is sooooo much better.

And it does appear to be isolated..:confused:
[Touch CDMA Windows Mobile ROM Development] tempests:
See, here is another weird situation. Using V12, stock dialer. I press the soft key from tflo or TT and the dialer pops up. Then I see the last 2 numbers dialed. I press either one and the number autodials. If I press the hard key (green) button 2 times, it always autodials my last number.
[Touch CDMA Windows Mobile ROM Development] cointelbro:
i think it's a bug, because it doesn't happen every time
[Touch CDMA Windows Mobile ROM Development] fwaits:
The poll on this thread is from WAY WAY back, not anytime recent when he put the GSM dialer back in to the v12 ROM. Just correcting that misconception.
[Touch CDMA Windows Mobile ROM Development] tempests:
I have no problems with the GSM dialer, using stock V12. It is way better than the CDMA dialer, which is slow, locks up at times, etc. And there are so many more features in the GSM dialer.

With that said, NFSFAN does this for free. So it is his right to include whatever programs, enhancements and dialers he chooses. We, on the other hand, have the right to use it or not use it. I for one am a big FAN of NFS. So I decided to volunteer, on my own, as many others here have done, and try to help resolve bad install issues, when I can. Because 99% of problems are from bad installs.

It doesn't seem like many of you have donated to this cause. I'm guessing he has 80 plus hours in the kitchen, not to mention the hours of testing he has to do, so he doesn't get flamed all to hell with "this doesn't work" or "I have no GPS or text" or "It bricked my phone" or my favorite "I'm not happy with your ROM. Can you send me all your work, so I can create my own". And he does it all for FREE!

I know it has been said before, but NFSFAN's ROMs are the best out there for the Vogue. So rather than bug him for tons of changes, let's support him, in the decisions he makes. He doesn't have to offer a Vogue ROM anymore. And, at anytime, he can decide to stop migrating his ROMs to the Vogue. After all, he has upgraded to the PRO.

When he does that, I'm buying a PRO!
[Touch CDMA Windows Mobile ROM Development] bobzero:
I was also thinking for a long time that that poll was biased in that some people may have voted for the GSM dialer simply because the alternate option was referred to as "old". Generally anything "old" is not a preferred choice when it comes to technology.
[Touch CDMA Windows Mobile ROM Development] jstn76rs:
I wasn't flamming at NFSFAN, I was throwing out my opinion on why the poll was the way it is. I was just saying that the poll was irrelevant. I am totally happy with whatever dialer is put into the rom.
[Touch CDMA Windows Mobile ROM Development] jadesdan:
I agree that the theme here should be "If you don't like it.....COOK YOUR OWN!"

I tried cooking my own, several times, and that made me realize more than ever how brilliant NFSFAN is. Sure I don't care for everything in his ROM, but it works better than anything I've come up with (or Verizon for that matter).

On another note, I've never had a problem with the GSM dialer (not ever the garbled text problem). But the morning I decided to test 911, and it froze. It wasn't a big surprise, I sort of expected it to. So I decided to try the dialer found here: http://xdaforums.com/showpost.php?p=4193170&postcount=8461

I have to say that it wors beautifully (even 911) and even has S2A. The only this is that it auto dials when you hit the send key, but I think I can deal with that.

I'm eagerly awaiting V13, but if it never came out I would be quite content!
[Touch CDMA Windows Mobile ROM Development] dmbpj:
I am going to try my first ROM flash this weekend. I have a Sprint Vogue (Touch). Currently I am running WM6.1 and ROM version 3.03.651.4

Anyway...this thread has a lot of posts and I have been reading the last few pages and to find a couple answers and then I thought that I might just post my questions. People may flame me, but I would appreciate just a reply with Yes/No answers.

Thanks in advance.

With V12 or V13 (if out) of WM6.5 (NSFAN) do the following still work smoothly:

1) S2U2:

2) Google Maps:

3) NuevaSync use with Windows Exchange Server (for contacts and calendar):

4) ActiveSync:

5) Internet Sharing (so I can hook up my laptop to my phone for internet access):

6) Lastly - can I flash back to the official WM6.1 ROM if I ever need to?: