yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] j18yo:
anyone else have a problem with volume?

maybe just coincidence but the 2 times so far ive tried to use the slider on the side of the phone it's done nothing, and then i notice everything i click or if i try to slide the screen its delayed until i restart...

is this just me?
[Touch CDMA Windows Mobile ROM Development] cbaty08:
Just you homie
[Touch CDMA Windows Mobile ROM Development] br125:
somebody posted that after updating the weather tab, after a certain amount of time the home weather will update itself.. I cannot confirm this

I just leave my file explorer in the windows startup folder, as I use total

commander for everything else, and whenever I update the weather tab I

open file explorer and its right there, press the script and I'm done..
[Touch CDMA Windows Mobile ROM Development] bobzero:
I believe I have discovered a bug. The option in sounds "Single volume" is broken. If someone will please confirm this I will add it to the bugs list for v17.

When the option to use "single volume" is turned on, the system volume and ring volume will go out of sync when you use the hardware volume control to volume the volume to adjust the volume to vibrate or silent, and then back to audible.

It took me a while to realize it was this option that was causing my phone to emit white noise instead of ringing despite the phone being set to ring out loud. In the sound options, my ring volume was set to 0% and the system volume was at 100% despite the single volume being turned on.

Bell v17, CDMA dialer.
[Touch CDMA Windows Mobile ROM Development] Gersonian:
I have mine set to single volume. I went into a meeting and turned it down with the slider to vibrate and i got an email while in my meeting and it only vibrated. When I got out I turned it back on to 100% visa-vis the slider and i just tried calling myself and the phone rang at full volume. I am not sure if this is what you are looking for, but I thought i would share since I was curious if I would have this issue.
[Touch CDMA Windows Mobile ROM Development] bobzero:
Thanks for the input. I was just playing with it some more and I noticed that it wouldn't go out of sync everytime, but after I adjusted the volume up and down a few times, surely enough, it went out of sync. Ringer at 20% and system at 80%.

If I do the adjustments with the sound config open in the background, it seems to adjust in sync, even re-syncing them if they have gone out of sync.

However if I close the window, and set the single volume to silent, allow the volume panel to close, and then set the single volume to an audible level, it will show them out of sync in the sound config panel.
[Touch CDMA Windows Mobile ROM Development] 2Sancho:
consolidate and summarize the problems

There is a noticeable battery drain compared to the previous releases.

Can this rom come with a fully funcional dialer regardless of looks. I cant answer a second call or switch between calls. Even the stock dialer from HTC touch/vogue worked and looked just fine to me.
[Touch CDMA Windows Mobile ROM Development] WnG88:
Running into the same problem with the FLIP Clock moving forward an hour. It almost looks like the Manilla clock is reading EST, then updating for Daylight Savings Time. I bet this problem disappears when we go to regular time.

The clock doesn't actually update on mine until I change screens or press somewhere on the screen. I've seen the clock a couple of hours or more off, then I shift screens and it shows -1hour and flips to correct time.
[Touch CDMA Windows Mobile ROM Development] tempests:
1. Don't know about the low volume on hard wired headsets.

2. I can confirm voice command over bluetooth problem. I use a Moto S9HD and it does not work.

3. Pressing the end key on my phone returns me to m2d home screen. Also as a side note, after about 30 seconds, whatever m2d screen I'm on, if idle, will automatically return to the home screen.

4. The limit is not a bug but a limitation. Everyone should have the same situation.

5. Must be a bug but I never use F Ex anymore because it is so limited. I use Total Commander, a way better file manager.

6. The un-necessary flipping around is because if you do not stay on the home screen, the graphics do not move. Therefore when you switch back to the home screen, the graphics will change to the proper time, sometimes appearing to jump around.

7. Others have experienced the alarm not working correctly. I can confirm it is working flawlessly. Remember to set all days you want an alarm to go off.

8. Some have reported text messaging notifications not always working, with regard to sound. Mine works perfectly. I noticed there are muliple choices in the sound settings for text and email. If in doubt, check them all off.
[Touch CDMA Windows Mobile ROM Development] refthemc:
It updates itself every 15 mins
[Touch CDMA Windows Mobile ROM Development] siniority:
the camera works great..no problems here.
[Touch CDMA Windows Mobile ROM Development] bigboy292000:
I don't think this is the problem we are talking about,

Example.

I take a phone right now. It is off (sleeping I guess you'd call it). I press the power button and the first thing I see is:

5:18

Which in about 1 1/2 seconds changes into

6:20

I press the power button again, phone goes back to sleep.

I wake it up by the power button again and I see:

5:19

Which in about a second changes into

6:21

Funny thing is that if the phone is sleeping and I press power, I see the stock small clock in upper right corner just for a second, before Manila kicks in. That shows the correct time, but then when Manila launches, it will (almost) always show 1:02 earlier and then flip to the correct time.
[Touch CDMA Windows Mobile ROM Development] ludester:
I notice this too...
[Touch CDMA Windows Mobile ROM Development] slow88lx:
Not quite.

This problem was brought up by me and another poster a few pages back.

Are you running a custom taskbar? It was discovered that some or all custom taskbars were causing the volume slider to freeze. If you uninstall the custom task bar your volume rocker should work without freezing.

I really hope NFSFAN addresses this in an update or something, because I REALLY hate the stock white icons.
[Touch CDMA Windows Mobile ROM Development] slow88lx:
The flipping clock is doing EXACTLY what they designed it to do. They wanted a fancy animation for the clock flipping and the result is the time displaying a hour ago so that you get to see the cool flipping effect. It's not a bug, it has nothing to do with DST or anything else. It's just how HTC made it.....get used to it! The only solution is an older build of Touch Flo or holding your breath until HTC realizes how silly it is.
[Touch CDMA Windows Mobile ROM Development] Monkeyzzzzz:
thanks for the info

Thanks for the informative response. It's very much appreciated.
[Touch CDMA Windows Mobile ROM Development] Monkeyzzzzz:
Mega GSM dialer

I'm not getting any vibrate on connect anymore. With V16 it worked great and most any older version in recent memory, but for some reason it's not working for me on this build...

Also, not extemely important, but I've never gotten QuickGPS to work on any NFSFAN build. Other custom roms and official rom works fine, but I get some "software may not be signed error" with NFSFAN. With previous versions I recall installing SDKCerts and still no worky.

If anyone can help... Much appreciated.

Verizon

XV6900
[Touch CDMA Windows Mobile ROM Development] siff:
XV6900 Radio

Hello all, I am looking to flash my VZW xv6900 to the latest VZW NSFAN's rom. The only question is the radio spec is for Radio 3.42.50. But the best I can find for the Verizon version is the 3.37.78, will this work? Is this just due to the different carriers or can I install the Bell 3.42.50 radio??? Any help would be fantastic!!
[Touch CDMA Windows Mobile ROM Development] njkid32:
NFSFAN, if you need anyone to test out any Alltel rom's just let me know. I've got plenty of time to mess with it.
[Touch CDMA Windows Mobile ROM Development] TruPlaya187:
Hi,

I'm new to this and I really like your ROM. I was wondering if it's possible to have the option or setup something as default that when you go on the messaging Widget and press on a text that the orientation goes into landscape automatically without installing a third party app. I have a HTC Touch QVGA with Bell.

Thanks in advance!
[Touch CDMA Windows Mobile ROM Development] leadpoizon:
A few tips for the Beta

Damn, this is like the awesomest release. I'm using the Sprint 1.09 beta 3 release on my Sprint Touch/Vogue, and it's pretty much flawless, and Footprints works PERFECTLY!

I did notice a few things, which I would like to direct towards the development of the Sprint beta.

The data connection seems to turn on automatically, even if nothing is accessing the internet, and it doesn't turn off, unless you turn it off forcibly. O_o

The Internet tab doesn't work when you try to launch the broswer, but that might be why it is disabled, possibly for development reasons.

The Touch cannot handle MPEG4 video in higher resolutions, like CIF, so I used Motion JPEG, which is fine (though memory-hogging.), but the Album video viewer doesn't support the format when you try to view it, so you have to use WMP. It would be cool if the album viewer supported the file format.

Btw, I also realized that this ROM is MUCH faster than the stock WM 6.1 ROM, lol.
[Touch CDMA Windows Mobile ROM Development] liquidi3ladz:
You can install the Bell radio on your VZW touch by unlocking the phone w/ coke unlocker, then flashing to the offical bell release and not letting customization run, (soft reset before customization runs) However your fine with using the 3.37.78 radio too, however there were issues in the past w/ gps and vzw customization in their 6.1 rom. I'm sure there are apps like vahalla gps that fixes that. Any 3.xx.xx radio will do since they are gps radios.

The stuck data connection is the result of using a GSM dialer.

For the internet tab, you can use M2DC' to set the dir of the browser you want to use. It's under the internet tap in m2dc. So if you wanted to use opera mobile, you would direct it to operal.exe where ever you may have installed it.
[Touch CDMA Windows Mobile ROM Development] mispook01:
TCPMP problems

I cannot get tcpmp to work with this awesomeany ideas? ROM keep getting crash.
[Touch CDMA Windows Mobile ROM Development] Ta-mater:
it is a known issue with tcpmp in WM6.1.

http://xdaforums.com/showthread.php?t=381292

go to that thread and get "update 3" or whatever.

works great!
[Touch CDMA Windows Mobile ROM Development] mispook01:
TMPMP not working

I cannot get TCPMP to work on this awesome ROM.

Any ideas?
[Touch CDMA Windows Mobile ROM Development] jashuacumbie:
NFSFAN - I figured out why I couldnt send out email...

My outgoing server requires authentication, in the account settings, there is an option for 'use same name and password', which I had enabled. When I turn that off, and specify the username and password, it works and I can send mail.

Seems like a bug. The username and pass I used were definitely the same.

Great ROM other than the tricky outgoing email that it took a freaking week to figure out... on my own. I also cant get the GPS to work and I cant seem to send out picture or video messages either.

Can anyone provide any advice on my other two issues or am I stuck figuring it out myself? :-P

Also, I know I am a noob, but I think I am capable of testing the Alltel ROM as well, as long as it is far enough along to not brick my phone. It's a work phone so I cant take that risk.
[Touch CDMA Windows Mobile ROM Development] jmitr:
When you flshed to 1.01 did you let customizations run? As this is an Alltel ROM you should have. The only time you do not want to let customizations run is when you are upgrading to another carriers radio, ie Bell 3.42.50 etc.

I am also going to assume you are unlocked? This is required to flash to a custom ROM.

The GPS should, as long as you have a 3.XXX radio and 6.1 ROM, work "out of the box". Mine worked no problem with the stock Bell 6.1 ROM, I've used 5 of NFSFAN's ROM's and have not had a problem with any of them. For the record under GPS settings, use COM4, Baud 4800, and if asked let windows manage your GPS settings.

Once launching Google maps, select "use GPS", place by the window and wait.

Good luck,

Jason
[Touch CDMA Windows Mobile ROM Development] jashuacumbie:
My GPS has never worked. My phone didnt have GPS functionality AT ALL out of the box from Alltel. It didnt even have options for it.

Here is what I did from start to finish.

Went to HTC site, downloaded latest RUU from them for my phone. This file: "RUU_Vogue_4350_ALLTEL_WWE_3.10.671.1_RS3.42.30_NV2.02_PRL30031_SHIP.exe"

Used PIMBackup to make backup.

Installed and let everything run.

Then I used this: "Vogue_unlocker_MFG_2.31.exe" to unlock the phone.

Then I downloaded and installed the NFSFAN ROM.

Then I restored using the PIMBackup tool.

I heard that the newer stock ROM included GPS functionality, apparently originally not included in the Touch from Alltel, so that is what prompted me to flash the phone. I called a co-worker familiar with the process and he told me about this site and to find the ROM with the most positive feedback and best screenshots, so I chose this one. By the time I was ready to flash to the new NFSFAN ROM I had already updated the stock ROM from HTC hoping to fix an issue with the phone calling random people from my phonebook when it didnt recognize the number (even when the number I was calling was in the phonebook the whole time).

Maybe that helps explain the circumstances and can help solve the problem. Were the early adopters of the Touch jipped out of the GPS hardware? Mine is maroon colored and I got it almost a year ago.
[Touch CDMA Windows Mobile ROM Development] wdbanks:
You need to upgrade your radio using the Bell ROM. Look though the thread here and you will find out how to do it.
[Touch CDMA Windows Mobile ROM Development] jashuacumbie:
Believe it or not, I have read about half of this thread.

I didnt want to be the new guy popping in to say "tell me how to do that one thing that you already told 5 other people the process for".

I actually asked already if I needed to upgrade the radio and was told that my version should work just fine (see sig for version, I cant remember). Started my own thread in Vogue Upgrades and everything. But I had just upgraded it to the version it is at now using the RUU from HTC I think it upgraded it anyway, it says 3.42.30 when it boots up, is that where the problem is?

Thanks for the advice. If I sound a little frustrated, I am, but I really do appreciate everyone that tries to help.

Also, I keep seeing mention of the Alltel ROM having problems with SMS... I can send texts just fine, but pics and video are no-go. Aren't SMS plain text? Anyone know why I cant send pics and vids?
[Touch CDMA Windows Mobile ROM Development] jashuacumbie:
Is it normal for the phone to show a Bell screen after going through the process of flashing the newest stock Bell ROM?

It shows during boot, as if it is the Bell ROM that is still loaded, but when I go into the system info for the phone it shows 1.01 Alltel for the ROM. I didnt see an Alltel loading screen at all.
[Touch CDMA Windows Mobile ROM Development] jashuacumbie:
Officially, the radio is not my problem. I am on the current 3.42.50 radio from Bell, have a Bell splash screen at bootup, and the phone is doing almost the same thing it was.

Instead of just not connecting, it now gives me a message that it is having a hard time connecting to a satellite, asking me to move to a place with a clear view of the sky. I'm in Erwin, NC, the sky tonight is very clear and I held the phone up above my head standing in my driveway (where the TomTom works).

I also found that if I disable the checkbox "let windows manage" or whatever it says, in Settings-->Connections-->GPS Settings, the phone gives me a message that it cant find the receiver. Settings are as advised, software port com4, 4800 baud, none under hardware. I am using the Google Maps app to try and get a fix on a satellite, it may be what produces the messages rather than the phone. Im not sure.

I should also mention that anytime I try to use the GPS my phone becomes nearly unusable. The buttons on the screen act up and it's hard to do things like press the start button, close a program, hide the keyboard, etc.

I saw another thread saying something about the PRI. My PRI is 2.02_011. Appears to me that is old, at least older than a few I have seen people claim to have. But I also understand that it is carrier specific? Anyone know what the latest PRI for Alltel is, and how I load it?
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
No, he should not upgrade the radio to the Bell one. He should stick with the one given by the provider, through updates.
[Touch CDMA Windows Mobile ROM Development] jmitr:
It sounds like you did everything right. The phone acting up is wierd. I don't think it's a ROM issue. Your old radio should have worked fine, the Bell should definately work.

Try this:

1. reflash the official Alltel wm6.1 ROM, let customizations run

2. Reset the phone, ensure the radio is 3.xx

3. place it into bootloader mode, ensure it is still unlocked.

4. Install google maps, try it and make sure it works. If your radio is 3.xx and you have wm6.1 it should

5. Flash NFSFAN'S Alltel 1.01 ROM, let customizations run.

If your phone still acts strange after step 4, something else must be wrong.

Good luck

Jason

If NFSFAN says stick with your Alltel radio, the's a good reason for it. The steps I gave you should work.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
I will be releasing the new ROMs tonight. If anyone has any suggestions or fixes to the Alltel MMS please let me know.
[Touch CDMA Windows Mobile ROM Development] jmitr:
Thanks for the excellent ROM NFS, will the official final release be any different from the test final? Any chance of getting the operator tab option put back in or a tutorial on how to do it?

Thanks again, after a few days of testing I can say this is your best release yet.

Jason
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Check your PM for Operator Tab.
[Touch CDMA Windows Mobile ROM Development] slow88lx:
Werd shun!!! I noticed this too.

I really miss this feature because it lets me know I can turn the screen off and put the phone to my cheek.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
People don't report what cabs/programs they have installed. If he flashed v1.00, there is no way you would get that unless you installed a cab that overwrote what was in the ROM. The datepicker & calendar have been ported by me from wvga to qvga.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Guys who are experiencing alarm issues, are you experiencing this without anything else installed on the ROM? You just flashed and tested this right away? Or did you guys install any cabs at all? (anything that could interfere)
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
This would be an issue with the HTCSoundSettings control executable that manila2d uses. This latest Manila2D is still beta material, not even close to final product.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
There really is nothing to address. The user who made the custom taskbar has to update the file as to spec with the proper OS build.
[Touch CDMA Windows Mobile ROM Development] :
NFS is there any where we can look to fix this wired issue... I want to fix it badly.. or is it a way I could get platformubuilder with your bats, take the Sys/XIP from v11 and add all the tweaks from v17
[Touch CDMA Windows Mobile ROM Development] tempests:
That is correct. read my explanation again. It's not a bug, annoying, but not a bug.
[Touch CDMA Windows Mobile ROM Development] tempests:
I know. This is always a problem when trying to help someone. I try to get them to explain their process to their point of failure. For me, I flash, I test for at least 24 hours then load software 1 at a time. I find an offending program, I delete it and move on. So far the only problem I see is the voice command not working with Bluetooth. But since I don't use that feature anyway, it doesn't bother me. And, as you know, a few people having problems does not constitute a bug, but rather something they did or didn't do.

Great ROM. You should be proud.
[Touch CDMA Windows Mobile ROM Development] tempests:
Works fine here. Make sure you have it set to vibrate and/or tone on connect.
[Touch CDMA Windows Mobile ROM Development] j18yo:
yeah thats the problem, theres a way around it tho im using the spb mobile shell so i got the volume thing on screen i just click it and adjust it

98% of the time its on vibrate anyways
[Touch CDMA Windows Mobile ROM Development] cointelbro:
ok i'm definitely rolling back to 16. 17 broke tethering for me (using a mac). EDIT: could be.snow leopard. i'll test it on a windows box
[Touch CDMA Windows Mobile ROM Development] cointelbro:
well something is broken anyway. in previous versions the device reported as a PAN on my mac and i could tether on verizon for free. cant connect to the mac at all now. windows works but it redirects to verizons pay portal
[Touch CDMA Windows Mobile ROM Development] mattcoz:
It's not a problem, it's a "feature". :rolleyes:
[Touch CDMA Windows Mobile ROM Development] dky1e:
It is happening on both mine and girlfriends phones--the alarm works once and then in 24 hrs it does not fire again.

I installed sprint provisioning, the mms cab (arcsoft 5.0.82.79), opera, bing search, mega dialer and restored previous data using PIM backup.

Using the first alarm slot, the alarm worked on first day but did not work second. I noticed that in the registry key HLM/Software/Microsoft/Clock/0 there is an item "AlarmOneTime" set to 0. /Clock/1 and /Clock/2 do not have the "AlarmOneTime" binary value at all...

Others experiencing the alarm issue, do we have anything in common?
[Touch CDMA Windows Mobile ROM Development] Table83:
Not going to lie, I might try v 1.00 just because it looks like you guys are having all the fun without me! Ok, first thing tommorow I'm hopping on the band wagon!
[Touch CDMA Windows Mobile ROM Development] cointelbro:
Well, bluetooth magically healed itself in my Win7 Bootcamp. The fact that it's broken on Mac probably means it's another thing that got changed about Snow Leopard. Why do OS updates always have to be two steps forward, one step back?

With this issue fixed, I guess I'll just chill with 1.00 for now. I'm eagerly awaiting your first 6.5.1 build!

(at least until the Motodroid comes out :cool:)
[Touch CDMA Windows Mobile ROM Development] Monkeyzzzzz:
It's set to vibrate on connect. I even changed the setting, and changed it back, but to no avail :(
[Touch CDMA Windows Mobile ROM Development] caquito07:
Where/how can I configure that?
[Touch CDMA Windows Mobile ROM Development] htcren:
It's not snow leopard, it reports bluetooth PAN fine with previous ROMs, so the issue is with v1.00.
[Touch CDMA Windows Mobile ROM Development] mfpreach:
I actually also posted this earlier .

it isn't osx's fault as v16 worked fine in snow leopard , nfsfan has changed something that has broken this .
[Touch CDMA Windows Mobile ROM Development] rmoore3d:
I can't believe how quick everyone is to blame NFSFAN after he works his butt off for us. I doubt if he broke it, he brings you the latest builds from HTC. They are the ones who probably broke the bluetooth PAN for OSX.
[Touch CDMA Windows Mobile ROM Development] noclueatall:
Mine did the same thing. It works once then 24 hours later it doesn't work again. I installed the sprint mms cab, opera, jade dialer, opera mini and restored previous data using PIM backup. This happened with Alarm 1 and 2. Also, I had M-F selected, so that is not the problem. My wife has a touch too, I will try it on hers without installing anything, but it will take 24+ hours to test.