yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] BoboBrazil:
I've been getting really bad reception since going to 6.5 v6x2. v4 worked fine, but once going to v6, i've been having nothing but problems. I'm on Sprint and my phone goes to roaming constanty in places where I've had perfect reception before. Even at home it doesn't have any bars where I used to have full bars before. I updated my radio to .50 and that didn't fix the problem...
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Did you try to install the Sprint Carrier cab to see if it helps your reception and network access to the Sprint network?

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] mike21pr:
i have been having signal troubles also, is there an updated sprint carrier cab with the latest provisioning that i can be pointed to??

thanx
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Not I - no missed calls or mail

Anything dialer/phone based you installed?

Any changes or regedits done or installed?

Did this occur immediately after flashing the phone or some time later ( a day, week) ?

Anything else not work stable? Internet, text, EMail?

Trying to help diagnose the issue but it doesnt give alot of data to go on

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
This is the latest I know of 1/09/2009

you can grab it

HERE

get it quick though as it is on Rapidshare and I dont know if there is a limit or not on numbers of downloads

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] BoboBrazil:
I will try this for a day and see if this helps. I had loaded it before I reflashed and I don't think I saw a noticeable difference, but I will try again.
[Touch CDMA Windows Mobile ROM Development] Shidell:
I still seem to have difficulty with Text Messages--the HTC input options work well, but it always defaults to "T9" mode rather than "ABC" mode.

I've tried multiple settings in the Input Manager to no avail, including some soft resets.

In v4, if I switched to "ABC" from "T9", the system would hold that setting unless I switched back, but since then, it will always default to "T9".

Anyone else having this problem? I tried re-flashing to the Sprint OEM ROM today and updated to R2, but it's still manifesting.
[Touch CDMA Windows Mobile ROM Development] NotLutzik:
Try setting HKLM\SOFTWARE\Tegic\eT9\IME -> set CarrierDefaultTextMode to 0
[Touch CDMA Windows Mobile ROM Development] br125:
After running 6.5 v6r2 for a while now (since the day after it was released), I noticed that the rom got slower in the messaging portion as time went on, entering and exiting sms specifically.

Finally it got to the point where I could not "X" out of my threaded message or else I would have to soft reset, as it would freeze. So I did the first reasonable thing and deleted almost all my text messages, everything went right back to normal and its as quick as it was the day I flashed. It just seems as if the rom can only handle so many text messages stored, maybe if the limit was reduced this problem wouldn't occur...

Just a heads up to NFSFAN as I know other people complained about slow messaging on this rom. Overall your work has been great, problems have been almost non-existent besides this!
[Touch CDMA Windows Mobile ROM Development] Shidell:
Thanks for the idea--although my 6.5 v6R2 registry doesn't seem to contain a "CarrierDefaultTextMode" field under "IME". ?
[Touch CDMA Windows Mobile ROM Development] anonymous19:
I've installed the latest rom, and its really great, except that in manila 2d, if i open an email, pressing the red "end" button doesn't show the today screen anymore - the only way to fix this is to soft reset a couple times - am i doing something wrong?
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Just for future reference, it is impossible that you are getting bad reception due to the ROM you have installed. Unless the ROM itself runs PPST (NAM Provisioning) on your phone, which 99.9% of custom roms out there don't there is absolutely no way that you are having worse reception. Reception has nothing to do with the ROM at all whatsoever.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
I think that people are forgetting that 6.5 is a pre-release build. These 6.5 ROMs are not final CORE builds yet, Microsoft hasn't released 6.5 officially. 6.5 is not made for the Vogue, or any phone being shipped now. If you need everything working without problems, including programs flash the 6.1 ROM.
[Touch CDMA Windows Mobile ROM Development] NotLutzik:
So create one ))
[Touch CDMA Windows Mobile ROM Development] greenfire:
Cricket Service + WM6.5

On the topic of: NFSFAN's 6.5 21202 V6 R2 GENERIC CARRIER ROM. (In Vogue Upgrading)

NFSFAN, You said:

"Also to all the Alltel users who are waiting for a ROM, I may be able to get something out this weekend, hopefully a beta. All depends on the time I have. I remember a user also asked about Cricket, chances are slim, since I wouldn't cook a ROM just for one user, if there are at least 2-3 people then I will." I would like to second the plea for you to cook up a WM6.5 version for the cricket service. You would make my millennium if you could do this!

I am sure there are many other cricket users in desperate need of your rom cooking skillz, they are all just to shy to speak up. Thank you so much for your consideration,

-Greenfire
[Touch CDMA Windows Mobile ROM Development] BoboBrazil:
Since upgrade to v6 I have experienced less bars and also my phone keeps asking to go roaming? Should I redownload the prl file? How can I get the latest prl?
[Touch CDMA Windows Mobile ROM Development] hexto:
I experience more dropped calls with V6 and V6R2 than with any other ROM I have ever used along with constant freeze ups and the soft reset acting as a hard reset issues. I think it is possible to have reception issues related to specific ROMs.

I'm not as experienced as NFSFAN but I did experience service issues with this ROM that can only be explained as "less bars"
[Touch CDMA Windows Mobile ROM Development] br125:
I am aware of that and the fact you know a lot more about this than I do.

With that said, I'm just giving feedback where I can.. not complaining about this or that, just adding a little info that may be useful.
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
OK, this one has me baffled - signal access is signal access, regardless of the software used on the phone

It could be 6.1 or 6.5/M2D hell it could be linux running android, its not going to affect how the antennae in the phone picks up the signal in the air..

now "dropped" or "missed" calls is something else entirely but signal strength is not going to be affected but the software on the phone - thats like saying My Sony HDTV gets less signal from my HD Cable box than my LG HGTV and if you were to open both sets the SAME hardware exists picking up the signal from the HDTV Cable box.

So unless someone is physically changing out antennae and chipsets between ROMs, the signal is the same as it was, unless your carrier in your areas are working on or adding towers or something causing signal drops or low power/access areas in your area the phone will pick up whatever signal there is to grab regardless of the app UI or software/OS used.

Ive been running 6.5 R2 without issue since its release, no missed calls, no message issues, no freeze up and certainly NOT suddenly without warning the phone just deleting half of my windows directory. Granted V5 and V6 has some issues that were easily correctable and V4 was damn stable as well, but so far V6 R2 has been best yet

Detroit Doug

P.S. I do not condone or recommend opening your TVs I dont know what chipset are in the TV's and it was simply an example LOL

P.P.S - Hexto, over at PPCGeeks you state your on Shadowfenders ROM are you still on it or did you flash back to this ROM?
[Touch CDMA Windows Mobile ROM Development] albundy9999:
Has anyone tried any program that would enable SIP Based VOIP on the HTC Touch running with NFSFAN's Bell ROM 1.31? Does it work properly with the phone.

Enable SIP-based VOIP on your HTC Phone -> http://wmpoweruser.com/?p=332
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Not sure it would, reading through the article in the link you posted one very major and very important line comes out

"Softreset your phone, and after that,

connect to a wifi network.

You will notice that in your Today screen, the VOIP line has changed from “No service” to “Available”. If you want to make a VOIP call, click on this line, and will change to “Selected”. All the calls you make from now on will be done using your VOIP line"

Not sure if your running a Wi-Fi card in your HTC Touch, but according to the article you will need Wi-Fi access

So, at that point, I doubt it will work natively as the HTC Vogue (Touch) Doesnt have Wi-Fi in it, so unless they found a way to pass it though network/internet access or your connected to a PC through the USB. Now I will admit I dont know about the app, I read through the article and the XDA thread mentioned but, nothing mentioned about Vogues, Touch Pro, Diamonds and Kaisers as well as some Nokia love over there on it, but then I have a phone contract with data, why exactly would I want VOIP on a Cellular phone?

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] albundy9999:
Thanks for the quick reply, Detroit Doug.

Well, I thought VOIP is using data and it's less expensive than making a call via the cellular network. It's like running skype or similar software. In this case, it's like setting up SIP servers, etc...
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Hey,

VOIP does indeed use network data access, but as stated it wants a connection via WiFi to access it through the app and "less expensive" way to make calls would only occur via a crippled/inexpensive phone plan to bypass using minutes or if your calling international numbers

besides the last substantial post was on 4/4/09 and that was just just Treo700wx love regarding the app, no real updates or even work on it for some time

This may have started off great, but looks to have lost steam and now is a piece of Abandon-ware apps out there unless there is something happening still with the Dev on it - might want to post for some detailed specs on that thread directly and see if they know more details if you dont get something specific here as the Dev would have all the specs and details if this path fails

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] noogies:
I've had to switch back to version 1.29 Version 6.5 V6R2 locked up on me several times, and a soft reset usually cleared my address book. Once while I was on the road, and needing to call a customer. grrrrrr

The switch back to version 1.29 was because I couldn't get V6R2 to sync, or I would have put up with the occasional lockup. Activesync kept giving an error, and 3 hours of work couldn't make it sync anything. Activesync worked first time after loading 1.29 back on my phone.

I also had a few problems with version 1.30 and 1.31. Occasional lockups, that weren't an issue with 1.29.

Before the ActiveSync problems, I tried running V6R2 without my 8gb microSD, (no mem card at all) but it still locked up within a few hours. (I'm now in the habit of flashing the phone twice before doing the screen alignment. Both times starting from the rainbow screen. Just to ensure that the flash takes properly.)

NFSFAN, Is there anything common between 1.30, 1.31 and the 6.5 V4 and up roms that might explain the frequent lockups? I found that 6.5 V2 didn't have the lockup problem also.
[Touch CDMA Windows Mobile ROM Development] craig0r:
Request for 6.5 v7

Hey NFSFAN. I'm really enjoying the 6.5 ROM. I'm still having GPS issues, however. I can get a GPS fix, but it takes much much longer than it would in 6.1, where I could run the aGPS fix found on the xda forums. However, DMRouter.exe seems to be missing from the 6.5 ROM. Is there any way you could include it in the next revision?

Thanks for all your hard work. If I can get GPS working in 6.5 as well as it was in 6.1, I'll definitely donate.
[Touch CDMA Windows Mobile ROM Development] karmatose:
I made a post yesterday regarding my phone, battery life and GPS. Just wanted to follow it up with some remarks on everything.

GPS actually works it just takes forever to lock. Would using a different radio revision help this? I'm currently using 3.40.something that came with the stock Telus ROM, but noticed there are newer versions floating around.

And with regards to battery life, I guess it's pretty average. It's using a bit more juice, but it's probably just me playing with it more. I'd say today since I've played with it less, it's on par with the OEM 6.1 ROM.

Once again, thanks to NFSFAN for your works.
[Touch CDMA Windows Mobile ROM Development] craig0r:
I upgraded my Telus phone to 3.42.50 and it still takes forever to lock. I'm going back to 6.1 until this can be fixed in 6.5.
[Touch CDMA Windows Mobile ROM Development] karmatose:
Good to know.. I'll save myself the unnecessary hassle of setting everything back up then. GPS isn't terribly important to me, but it'd be a really neat feature to have on hand for when I actually do need it.
[Touch CDMA Windows Mobile ROM Development] mikedav01:
This is a dual reply. The GPS mode in registry should be 4. 4 will use cell towers data to speed lock, 2 will use towers data only to update maps, etc. So, you do want it to be 4. This is done in the registry, not qpst. HKLM/software/htc/supl agps. change it if its 2 and softie, then should workgreat. This might help those who are having long time locking issues.
[Touch CDMA Windows Mobile ROM Development] demoniac9:
First time I've used WM 6.5 and I got to say it is pretty sweet. Very nice job on the rom NFSFAN

I have found a bug, not sure if this is due to 6.5 still being a pre-release, or is something you can fix. I have seen several other people mention this but no fix as of yet.

The bug is if the screen is locked and a incoming call comes in then it will show UNKNOWN caller, a default picture, and the phone number. If the screen is not locked then the incoming call is detected correctly and shows the correct photo & name.

This only happens if the incoming contact has a category assigned to it. I was able to test this by removing all categories from a specific contact and calling my phone. Everything worked as you would expect. Once I added a category back to that contact it came up as UNKNOWN again. (again only on the lock screen).

Not a huge deal but since others had mentioned it I wanted to bring to your attention that I think the problem is due with having categories on your contacts.

If anyone has any ideas or can duplicate this behavior let me know.
[Touch CDMA Windows Mobile ROM Development] nbpanjwa:
Problem running iGO Amigo v8.4.2.81333 on Sprint 6.1 v1.12

It works fine for the first time, but then it just hangs up needing to restart. Maybe it is looking for GPS radio and not able to find one??? Somewhere I on the net I found this..... "If the software is unable to detect your GPS receiver or your receiver fails to acquire satellite fix, shut down Amigo, go to AMIGO/SAVE folder and edit the system.ini by directly entering your GPS receiver parameters" but I don't know how to do this, where would I find GPS receiver parameters???. Will appreciate if anyone can help or share there successful experience with other GPS navigation software.
[Touch CDMA Windows Mobile ROM Development] br125:
maybe try to prime your gps with another program..

before you open iGO open up gps viewer, then after you get a lock open iGO

I'm not sure on the paramaters in the .ini file, but give this a try first
[Touch CDMA Windows Mobile ROM Development] nbpanjwa:
Thanks for your reply, br125 That is how I manage to start for the first time in freshly installed ROM, but thereafter it just hangs. BTW software is not installable and resides in Amigo folder in SD and will start by exploring exe file and executing it, I don't have shortcut for it yet.
[Touch CDMA Windows Mobile ROM Development] keith.mcintyre26:
Apps

Are there any apps available for WM 6.5 yet? What happened to the facebook app? I have ADD, I'm at work, and need to play.:D
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Interesting.. I have 3 catagories, PERSONAL, WORK, OTHER and as one would expect my home number is in my PERSONAL category and yet when I call my phone here is the display as it happens

I havent done anything extra to the phone other than installation of some games, browsers and the like, havent altered my dialer or its canvas

Now in Outlook I do have contacts there setup as my phone and sync to put them back and to back them up, but other than that nothing extra is done

Weird

Detroit Doug

PS - hate her music but she is F'ing hot regardless LOL
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
There have been some success and some failures in regards to getting apps compatible and working with the WinMO 6.5 UI

This is pre-release so cant expect everything to work perfectly when most app developers havent even seen the UI yet let alone worked directly with it

Have you tried the FB app on WinMO 6.5 and confirmed it fails?

Have you searched out the Dev thread on it to see if someone has found a fix or hack for it?

I dont really have much info on the FB app as I dont use it LOL but have read of issues but havent followed it very closely

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] demoniac9:
Huh, well thanks for checking it out and ruling out my theory. I just tried it again with a "personal" category and no category and it works fine if nothing is set but once I set it to personal it goes back to unknown. There must be something else going on. I will try a hard reset now to see if that helps. I also have all my contacts in Outlook and sync up via Exchange...

I'll see if a reset will do it... thanks.
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Can you edit my quote killing the pic LOL thanks

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] Sean.Thon:
You always seem to have the best backgrounds =p
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
google can be your friend LOL

it is mine

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] Sean.Thon:
hrm well I decided to take the plunge and upgrade from v6 to v6 R2 but figured what the hell I may as well upgrade my radio to 3.42.50 while I'm at it so here are the steps I did

1. installed bell OEM ROM with 3.42.50 radio from boot loader mode

2. after it booted entered boot loader mode again and installed 6.5 v6 R2 (did not let customizations run on the bell ROM) Radio reads 3.42.50

3. Setup V6 R2 let customizations run, soft reset

4. Hard reset

Everything *seems* fine so far still a little too early to tell my question is now when I boot up I have the bell splash screen, how can I replace this with the sprint splash screen?
[Touch CDMA Windows Mobile ROM Development] demoniac9:
Sorry about that, I've removed it :). I just did a hard reset and it is working now. Not sure what the deal was but it is working now.

Let me ask you another question as it seems like you have a similar setup, when I get an email the lock screen will change and have 1 on the lock for the new email. About a second or so later that number will disappear and if I unlock it will take me to the today screen. Once in there it shows I have new mail but the lock does not show I have new mail? If I get a missed call or voicemail that number stays on the lock screen until I dismiss it. Any ideas? Wondering if it has anything to do with exchange or something? Not a big deal or anything, was just curious. Thanks.
[Touch CDMA Windows Mobile ROM Development] steve98:
I am seeing this behaviour too, but I do not have any categories setup. My contacts are stored on my corporate exchange server and synced to the phone via activesync. When the phone is unlocked, contacts display correctly when an incoming call is received, but when the phone is locked the phone number is displayed but it says "Unknown caller" and shows a generic picture where the photo should be.

Very frustrating...
[Touch CDMA Windows Mobile ROM Development] struthersdln62:
this is an excellent wm6.5 rom. i only have one problem and wondered if anyone else had the same issue. the rom installed perfectly but when i installed the sprint picture mail cab, it installs successfully then when i try to send a picture message i get an error saying unable to connect to server, unknown phone, and it occasionally freezes the phone. everything else works great tho
[Touch CDMA Windows Mobile ROM Development] demoniac9:
I just did a hard reset and that seemed to fix the problem, no more unknown callers. The only things I had installed before I did the hard reset were some auto locking tools, flash, and titanizer. I'm not sure how any of those programs would cause this behavior but if you have any of the same ones installed you might want to uninstall and see if that helps?
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
I actually think some of the recent "locking" and "lock screen" apps may be the cause - just conjecture at this time though as I have not installed any of them and have not experienced the issues people are referring to like you had

No problem, My fault for not editing it first like I normally do LOL appreciate it though

Ive noticed it as well and I think it has to do with if you have the mail app in question running in the background and it gets a new message it does as it should alerts you to the message in question, but because the app is also running it considers it read or acknowledged and removes the alert from the lock screen itself on the slider, if you make sure that when you check/read your mail go to the upper right and close out the app and lock the screen, then send yourself a test email it will alert then show on the slider and stay there

I really dont think it is a bug as the app is doing as it is supposed to be doing the whole time its just the way it is written than when the alert is dealt with and the message seen (by the related app not your eyes) it disables that alert

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] Spalla:
I want to see an Autolock mechanism implemented into your 6.5 roms. I usually leave my phone in my pocket, and if I don't have a program like S2U2, the phone will start opening up random programs.
[Touch CDMA Windows Mobile ROM Development] dubbwilliams:
Well I'm up and running on WM 6.5 R2, did a stock flash (no customization) before I went to R2.

Everything's running great on my end. Haven't really noticed any slow downs. Hitting "Ok" to close a text window still causes the messaging screen to not refresh the column headers. However, it takes a whole lot less time then it did on R1.

Skipped the titanium weather this time around. I've been using your opera build NFSFAN on WM 6.5 and just had it crash on a CNN story. Not sure if you can do anything about it, maybe I can find a crash log of some type for you?

One really annoying bug that's been in place since using WM 6.5, is the qwerty keyboard switching to "T9 Mode" every time you open a new message window and hit the SIP to bring it up, it always reverts to "T9 Mode".

T9 attempts to predict/spell words for me and I hate it.

NFSFAN, is there any way to default it to "ABC Mode" at all times?
[Touch CDMA Windows Mobile ROM Development] dubbwilliams:
You have two options here.

Option 1:

Under Start -> Settings -> Lock

Check "Prompt if phone unused for". If you want it to lock every time you turn the screen off with the power button then leave it at 0 minutes. You must use a password to use Option 1, so may not be the best choice. Up to you really.

Option 2: (This is the one I use)

Start -> Settings -> System -> End Key

Change radio button selection from "Always display the Quick List" to "Automatically execute the selected action:" and then move the sub radio button selection to "Lock device" (Note: You need to hold the end key for like 3 sec or something like that)

By the way, I think WM 6.5's new lock screen makes S2U2 obsolete which is why NFSFAN did not include it.