yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] tempests:
You don't. the new TouchFLO doesn't have that feature anymore. You would have to change the manila version like some have done here. But there is no guarantee that it will work without breaking something else.

I for one don't miss it. I just click the phone soft key and go to history, or press the top bar if there is a missed call icon there.
[Touch CDMA Windows Mobile ROM Development] scubarocks:
I also have used this method since my first NFSFAN rom and have never had an issue
[Touch CDMA Windows Mobile ROM Development] wamblej:
Keyboard

-removed- updated later.
[Touch CDMA Windows Mobile ROM Development] slow88lx:
Am I the only one? or is this normal?
[Touch CDMA Windows Mobile ROM Development] eric2k:
This is normal. It will not be changing.
[Touch CDMA Windows Mobile ROM Development] slow88lx:
Well that totally blows! No way to make them work outside of TF, I guess?

Has anyone gotten a theme to work on this newest TF? It seems most themes don't work on our ROM

Specifically, this one?? ↓
[Touch CDMA Windows Mobile ROM Development] zenulator:
I have to say this is very nice.
[Touch CDMA Windows Mobile ROM Development] HDRules:
I used the customizer to remap the right soft key and do not have the date issue you mentioned. My setup is no doubt different from yours as I use the regular today screen including the phoneAlarm plugin and use phoneAlarm to switch back and forth between the traditional today screen and Manila. But the changes I have made in the Manila Customizer are working without side effects.
[Touch CDMA Windows Mobile ROM Development] wherestheanykey:
Ok thanks for the long reply. I have been using the USB update method and have flashed the factory ROM first before any new ROM, and have also done the three flashes with set up running each time, and then do a hard reset during the the last boot after the set up on the third flash. So I am positive I have taken no shortcuts during the loads. I don't install the carrier GPS or carrier provisioning cabs, and have never had trouble connecting data or anything.

Should I still be installing these two cabs anyway for some reason?

I use the least glitchy dialer cab, the NFSFAN CDMA dialer, and don't install any menu enhancements or fonts or themes and used the IE browser that came with V16 and the NFSFAN Opera Fix cab and browser on V17. I use the keyboards that come with the ROM and only really install things like SPrint Nav, Sprint TV, Sprint picture mail, the OZ IM that came on the touch originally, Sprint Cup Mobile, Sprint NFL Mobile, and windows live search. I did end up trying a couple different versions of Manila 2D at the end in a failed attempt to get the date fixed on my home screen, but any issues had presented prior to that.

So I am realitively sure any issues I have run into are not necessarily the fault of a poorly executed flash or because of some wierdo third party application with a sketchy history for being dependable. What I do know know is that what caused my most aggrivating issue to date was by simply using the Manila 2D Customizer application that is loaded right along with the ROMS. I reflashed following the process I described above and the date was back on the home screen immediately after the first flash. It was there until about two hours after I finished the load today, when I changed the right side soft key from camera to contacts, as I had done in the past also. As soon as I did that the date was gone instantly. It was my mistake to assume if the utility was there, that it worked. So in the end I did break it myself, but I am surprised if this is what happens when you change the soft keys using the customizer, that no one else has noticed this.

And I appreciate that you explained your method step by step in detail, so at least I know now that I was performing the loads using the best proven process available. And if there is a way to edit the soft keys via a registry edit instead of the customizer, I would like to know how please, since the right key being the camera button doesn't do me much good because I don't often use the camera and when I do I usually slide over the the photo tab in TF anyway.

Thanks again for all your help, and thanks again to NFSFAN for doing such a nice job on the ROM.
[Touch CDMA Windows Mobile ROM Development] thepipes:
Where's the link

I just got back from somewhere, and I'm looking for the link to v.17. Any idesa?

Dan
[Touch CDMA Windows Mobile ROM Development] slow88lx:
Page 1 :eek: It's crazy sensible, I know.
[Touch CDMA Windows Mobile ROM Development] wherestheanykey:
Nice, maybe it's time to give up. I have installed the ROM

EXACTLY

as it's supposed to be and have installed nothing but the NSAFAN Weather fix, the NSAFAN CDMA Dialer cab, and the NSFAN Opera cab, and try to edit the right soft key and the whole thing breaks, you install aftermarket software and who knows what and it works just fine for you. When I post for help, it's just assumed that I must be foolishly doing something stupid and there is no merit to my problems.

Does anybody else care to try to make this edit to their phone and see what happens to them. I changed the right soft key in the Manila 2D Customizer to read "Contacts" and linked it to the file associated.

Thanks if you do.
[Touch CDMA Windows Mobile ROM Development] tempests:
It makes perfect sense. Version 1 on page one;)
[Touch CDMA Windows Mobile ROM Development] tempests:
Instead of dwelling and getting all upset and giving up, my solution is move your contacts tab right next to your home tab and leave the soft keys alone. Problem solved. You have to remember these are not stock ROMS, so they are more fragile, when attempting to change things. I guess my biggest reason for a stable phone is I like NFSFAN's ROMs exactly the way they are. If I didn't, I would cook my own. Don't get me wrong, I install quite a few programs, but I do one at a time in case one doesn't play well with 6.5.

Now I have a list of ones I use that work.
[Touch CDMA Windows Mobile ROM Development] wamblej:
Txt problems

For some reason sometimes when I am texting - and I use the compact QWERTY keyboard - it just enters numbers. I am not sure why this happens, but it sometimes happens when I do a new message, and sometimes when I do a reply. Not all the time though. When It does I have to switch to the full keyboard to finish my message. Any ideas why this could be happening? I don't remember having this happen with past version of the rom. Any help is greatly appreciated. Thanks!

- and sorry for the double post - for some reason I thought my previous one (on the last page) didn't post.
[Touch CDMA Windows Mobile ROM Development] voguefan:
Start menu icons freeze

the start menu icons are freezing on top of each other any idea

Thanks:confused:
[Touch CDMA Windows Mobile ROM Development] voguefan:
my start menu icons are freezing on top of one another any idea?
[Touch CDMA Windows Mobile ROM Development] tempests:
need more input.

how did you flash?

Didi you install or change anything and then the icons started freezing?
[Touch CDMA Windows Mobile ROM Development] jmitr:
Yes, I changed the Left soft key to "Call History". I still have the date.

Sort of..........see above, this WILL NOT give you back missed call and voicemail notifications

Yes that is correct

Yes, I make my own. I'm not a big fan of the brown. I prefer the standard TF black / green. I also made my bottom task bar flat black to match NFSFAN's flat black tsk and the top curtian totally transparent. I also tweaked the transparent clock to my liking.
[Touch CDMA Windows Mobile ROM Development] ihateu3:
Just so everyone knows here, I am running a legit full retail release of windows 7 and I was unable to flash back to the stock rom within windows 7 (I didn't try NFSFAN's ROM in Windows 7 though) so just a heads up with the new operating system
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
so you are on a custom ROM, attempting to flash to a Stock ROM but somehow the OS is stopping you???

Can you be a bit more clear, you cant connect to your phone via MDC or you can connect just cant flash?

Can you flash any ROM have you tried that?

If you cannot connect your phone to Win7 - have you gone into the device manager, network adapters, microsoft mobile device network adapter - rightclicked and updated software? its just going to reinstall the driver over itself as Ive noticed thats the quick fix for me in regards to being unable just after a flash on Win7 for me

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] gjbnh:
Was this also true if you ran the stock rom in compatibility mode?? If so, this is a MAJOR problem!!
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Firstly relax .. this is not a "major" problem .. if the case that retail Win7 cannot flash a ROM to a phone and its an issue that didnt exist with Win7 RC1 or prior.

If there is an issue with retail Win7, there isnt anything this forum or NFSFAN can do about it - its a Microsoft issue

So before claiming the possibility of it being any problem let alone a major one, we need the user originally posting this to update some info on what exactly is going on and where it is failing at before claiming the sky is falling, ok

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] tempests:
The poster has other issues. Win 7 works fine. He must be trying to flash a different way. I flashed my phone back to stock and to the new ROM, using the same method I have always used (the executable ROM file from HTC and the RomUpdateUtility.exe). I do not use any third party software, device centers, etc. I just connect the phone and once connected and showing up as a device in My computer, I execute the proper file. So he must have other issues.
[Touch CDMA Windows Mobile ROM Development] bigboy292000:
+1 on no Windows 7 isues. At least on my 32 bit install (fnal, RTM), I was able to flash no problem.
[Touch CDMA Windows Mobile ROM Development] tempests:
Found my first Bug, Just Kidding

I was having the problem with my bluetooth not allowing me to initiate a voice command. So I installed Microsoft_Voice_Command-MSVC1.6.19214.cab, as mentioned earlier, to fix the problem. It installed flawlessly and did, in fact, fix the problem.

But then this strangest thing started to happen with my phone. It started to talk to me when I received a phone call. It told me I had an incoming call and exactly who it was.:eek:

Now if I can only get it to take itself out of the pouch and hold itself to my ear.:D.:D
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
I also use Win7 64bit and am having no issues as well BUT I am waiting on the poster to supply more information to narrow down the actual cause as well as stem the "panic" "rom is broke" "win7 sucks" BS that will occur until there is a known problem to point the issue at

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] tempests:
Ah you'll never stop it!

Look at the many people, that are reporting all sorts of bugs with V1.00:eek: Rom broke my phone, this ROM sucks, So and So's ROM is better and then leave out the fact that they installed another menu system, tweaked something, made a registry change! Sound familiar!:rolleyes:

I guess my phone is different than the ones they have. Of course now I have this issue where my phone talks to me.;)
[Touch CDMA Windows Mobile ROM Development] gjbnh:
I agree it is a problem for MS, which is what I meant. NFSFAN's rom is rock solid as far as I can see. It is a MAJOR problem because anyone who uses Win7 for an enterprise or business might NOT be able to fix their phone.

As for Win 7, my experience had been mixed. On a 3 yr old Acer laptop it runs flawlessly, and has for about 3 months. On on HP less than 6 months old, not so much. I had to go back to vista because it was so unstable. I tend to be very aggressive about updates, drivers and such, so I guess I'll wait until I get my pre-order before I pass final judgment.

I agree with Tempests. People need to follow his advice and run the rom for a day BEFORE they start try and add extra stuff to it, in case there is a comparability problem; it makes it easier to isolate the culprit. Again, my experience is NFSFAN's roms tend to be really solid and stable. And let's face it, MS's record for keeping backward comparability is a little less than stellar.
[Touch CDMA Windows Mobile ROM Development] mikedav01:
Have to chime in. Been using W7rtm and now the real Ultimate. Never a problem with synching, flashing etc. W7 is kinda nice really.
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Again, I have to point out, it is NOT a major problem...

1) others including myself are NOT having an issue with Win7 and our phones, synching or otherwise (not saying no one is but if there is 1 version and 1 person of Win7 being successful in flashing and synching, the the issue is obviously not with MS Win7 or it wouldnt work across the board for everyone)

2) for those in the enterprise or business community - the idea of having and maintaining a smooth, working IT environment is stability, that in part is achieved though having everything similar across the board - custom ROM especially beta ROMs are not responsible within an enterprise or business environment

We are still waiting on what the problem the use had was - so we are still waiting on that use to reply with a bit more info than "it wont work on Win7" as others including myself can confirm it DOES work on Win7 ...

Being as some have already chimed in with Win7 flashing and synching with ROM as successful - that eliminated both MS and NFSFAN's ROM as the issue - now the step of tracking what occurred is required

- corrupt download?

- antivirus programs?

- interrupted flashing or bad flash of phone?

- installation of incompatable or a bad/failed install of a incompatable them or application or dialer?

- physical damage to phone or bad memory on phone?

- type of installation (via activesynch or SD-Card AND if failed on one type was the other style of flashing even attempted?)

obviously there is something far more going on in the background we are not yet understanding and until that information comes to light no one can correct the issue to start with ... but again, NOT a major issue when in truth, business should be sticking with a stock environment for the phones they use rather than using custom ROMs unless it would be in-house or contract developed and supported to be compatible with the environment they have directly ..

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] tempests:
You forgot to mention the experience of the user. This has always been a problem with computers and now modding electronics. The computer industry is such a multi-level industry when it comes to knowledge. You have the novice that knows too much and sometimes wants to blame the manufacturer or programmer. You have the user that is dangerous, because they think they know more than they do. You have the expert that knows it all and wants to improve what is already working. Then you have me (I'm just kidding).

But seriously, in my business, we have seen users of computers cross the line into tech work, because they think they can fix it themselves, only to create more damage and lose important data. It's sort of this way with these phone mods. You have novices to experts flashing their phones. So you will get all sorts of problems from both. The novice being inexperienced and the expert wanting to tweak until they break it.

Me? I deal strictly in logic. There is always a logical reason why something is not working correctly. It's figuring out how to get the person with the problem to explain everything they did before the problem started.
[Touch CDMA Windows Mobile ROM Development] gjbnh:
2) for those in the enterprise or business community - the idea of having and maintaining a smooth, working IT environment is stability, that in part is achieved though having everything similar across the board - custom ROM especially beta ROMs are not responsible within an enterprise or business environment

obviously there is something far more going on in the background we are not yet understanding and until that information comes to light no one can correct the issue to start with ... but again, NOT a major issue when in truth, business should be sticking with a stock environment for the phones they use rather than using custom ROMs unless it would be in-house or contract developed and supported to be compatible with the environment they have directly ..

Detroit Doug[/QUOTE]

I bow Sir, to your wisdom.

But you know how boys like to play :D
[Touch CDMA Windows Mobile ROM Development] rmoore3d:
Does the Win 7 user know he has to run the exe file as administrator? If he came from XP he may not know.
[Touch CDMA Windows Mobile ROM Development] socrate007:
Message for our "tech support" guys

I would like to say thank you to you guys,

I am very thankfull to you people on this forum for helping out others (like me) that experience trouble flashing or using this ROM on their vogue. You have to help a lot of people and you get to repeat the same thing over and over again.

I understand that is drains a lot of energy but please remember that reporting an issue is not necessarely "complaining". It is part of the process of using products on a forum, expecially betas.

As i have noticed myself, there are a few people that really are posting thankless messages when reporting problems but most people are doing this with good will.

The major problem I think is the volume of messages. There are so many persons that need help and post messages here that it gets impossible to search for an answer in this forum, forcing you to repeat the same thing over and over...

Codybear already did lot of good work but it's time we update the FAQ, giving priority to:

- How to flash the ROM correctly (this has not been changed for a long time; it doesn't reflect what is being told here and it should mention that if having problems: it is suggested to do it "the long way", installing .cab apps later, one at a time, to pin point problems). + flashing with Vista, Win7...

- Answers and suggestions that you guys are repeating here all the time.

- Some reasons why

it could not work

even when the flash has been done the right way and what to look for/try to do to fix it.

I am willing to help you guy with this.

Then we really need to make this updated FAQ very visible in the vogue section

(sticky it at last!!)

and on NFSFAN's ROM 1st page. It needs good marketing so people will read it before posting.

I think then, this forum can be efficient again at fixing real problems, if there are any.

Thanks again!
[Touch CDMA Windows Mobile ROM Development] mastershak:
where do you get the win7 drivers for the touch? win7 for me says it can not find them and tried to install a qualcomm modem. THANK YOU
[Touch CDMA Windows Mobile ROM Development] Bob2D2:
Has anyone else seen a problem where after applying a custom theme to m2d with the newest 6.5 where touchflo just won't launch?

I'm running the newest 6.5 on a verizon vogue, flashed 3 times, had touchflo working last night. This morning I tried changing themes to http://xdaforums.com/showpost.php?p...ck to "tap to launch touch flo"

Any ideas?
[Touch CDMA Windows Mobile ROM Development] bobjr:
After installing V1, I'm just noticing that the camera doesn't work anymore. Tried going back to V16, but it still doesn't work. What is happening is when the camera fires up, it displays just a white screen (with a pink dot in the middle). I'm sure that the camera did work with V16 immediately after flashing, but unsure if it worked before flashing V1.

This must be a hardware issue, correct? Or has anyone had this and was able to fix. I've searched this thread and PM'd another user that was having this same issue.

Thanks
[Touch CDMA Windows Mobile ROM Development] irodex:
I just installed the ROM and I love it, however I am having a problem accessing the volume control. The only way right now I can turn the volume up or down on the phone is to use the slider on the left hand side of the phone. When I click the volume icon on the top all it brings me to is the notifications window, which does not have any way to adjust the volume.

How can I adjust the volume?

Thank you!
[Touch CDMA Windows Mobile ROM Development] mattcoz:
Awesome! :D
[Touch CDMA Windows Mobile ROM Development] hemirunner426:
The only thing i can think of is to double check the MMS registry settings... everything looks to be there, however the "Allow delivery report" checkbox was checked and typically that needs to be disabled...

You kow, i checked out the touch pro at an alltel store and it does have arcsoft 5 with the same settings as I have... i bet arcsoft 5 would work with the vouge if we can determine the correct registry settings.
[Touch CDMA Windows Mobile ROM Development] bgolden8:
is the new rom your releasing just for bell or is it going to be for all of the providers
[Touch CDMA Windows Mobile ROM Development] c_swin:
...............................................all providers.

READ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Touch CDMA Windows Mobile ROM Development] picturethismister:
Is the new Bell ROM gonna support Google latitude:rolleyes:
[Touch CDMA Windows Mobile ROM Development] soccerman821:
just a weird thing that has occurred with the new verizon beta(feb 4th one). My vogue has frozen up after a day or so being on and i soft reset with the pin hole and it came up as if i had just flashed the rom.. customization and all. it has done this twice. i did a hard reset after this happened both times. looking forward to new beta tho, thanks for your work
[Touch CDMA Windows Mobile ROM Development] kenlewisesq:
I have a Sprint model but the same thing was happening to me as well. I was able to fix the problem by flashing the stock Bell rom (did not let the customization run) and then flash the beta rom.
[Touch CDMA Windows Mobile ROM Development] PhoenixTJ:
1.28 is running good on my bell vogue. Same as it usually does. One thing I'm wondering though is 1.28 tethering safe?
[Touch CDMA Windows Mobile ROM Development] rexdale_tiger:
is there a way i can get my contact like this.

it looks nicee
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Buy a Diamond.
[Touch CDMA Windows Mobile ROM Development] rexdale_tiger:
LOLLL i wish i had that much money

i was just wondering

cuz u seem to do lots off cool things so thought u could probably do that too but i guess not its ok thanxxx though
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Sure I could do it, I'd port TouchFlo3D, if our phone supported it.
[Touch CDMA Windows Mobile ROM Development] rexdale_tiger:
ohh ic

now it makes sense to me loll

thanxx bro

my next phone IS Diamond though lol:)
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
NFSFAN,

I noticed a 8:33PM update as well as updates regarding the Feb 12th build info - Im assuming the builds (namely Sprint) have just been released?

thanks

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Yep. Sprint is up.
[Touch CDMA Windows Mobile ROM Development] Thinspirits:
So i just updated with the 1.28 Bell Rom on my Telus phone.

I soft resetted the phone before the customization and when it restarted I added my Exchange server through ActiveSync and it doesnt seem to work.

I get error Support code: 0x85010013

Am i doing something wrong?
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Let customs run.
[Touch CDMA Windows Mobile ROM Development] derekwilkinson:
Awesome! I hope to upgrade my ROM this weekend :)
[Touch CDMA Windows Mobile ROM Development] Thinspirits:
I figured - i would try that - in the process of doing that right now.

Will post what happens.
[Touch CDMA Windows Mobile ROM Development] youppi:
Why not use the Telus Rom? I'm still using the 1.03 release. It work's amazing.