yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] poppy007:
Codybear, the reason I wrote up the fix I used was that, I can't overwrite, delete, rename or in any other way change or modify titaniumweather.mscr (located in \windows) even in safe mode. I am pretty sure the reason is that in the file properties I verified that it is read-only, system, and ROM as indicated by total commander. Because it was a rom tagged file I couldn't even delete it when I booted into safe mode. So to get past all that I disabled weather, installed weather 4.2 cab which installs to \program files\titanium weather. That titaniumweather.mscr file doesn't have the rom tag in properties so it was easy enough to overwrite with Detroit_Doug's but that one didn't work with 4.2 (icons not working) so I used sector's and it finally worked.

What I still don't get is why is my titaniumweather.mscr located in \windows is rom tagged in properties and everyone else's isn't? Or if everyone else's is, then why can everyone else overwrite a rom property tagged file, which according to everything I read at the MSDN forums says, is impossible to do?

LOL, am I the only one with that problem of titaniumweather.mscr being locked as a rom file and can't be deleted or overwritten?
[Touch CDMA Windows Mobile ROM Development] 4thought:
I connected via activesync, deactivated titanium, copied TitaniumWeather.mscr to the Windows directory (thru activesync), reactivated titanium, done.
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
There has to be something installed or applied that changed something on your phone as several people have reported no issue making the file work and copying over and Ive personally done it on 4 Touch phones running custom 6.5 Roms today alone out playing poker in between hands - you are disabling "windows default" under start>settings>today right?

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] incubus26jc:
this is what works. Ive tried everything you guys have said to do and this is what really works for me. Download titanium weather 4.2. Then download the attached .mscr file from modaco forum. download the mscr file from codybears first post above. disable titanuim. disable weather with titanium customizer. install titanium weather 4.2. Place the mscr file from codybears post in windows. place the mscr file from this post in program files/titanium weather 4.2. Soft reset. enable titanium weather with titanium customizer. enable titanium. run full update. FINALLY WORKS!! thanks everyone for all your help getting this to work.
[Touch CDMA Windows Mobile ROM Development] codybear:
Well if its a rom file, you're able to copy over it.

Then if you delete the modified version,

and soft reset the original rom file shows back up.

But you're never able to delete the original rom file.

Did you disable titanium and also use total commander

(start>system tools)

Another thing I did was just navigated to the zipped file on my sd card,

opened the zipped file through total commander,

and then pressed and held on the mscr file,

and pressed unzip.

I pointed it to the windows directory

(press tree button, highlight windows and press ok)

Then it asked if I wanted to overwrite and I chose yes.

Done deal. haha.

Yeah, not sure why it's not working for people....

Hmmmm, whoever is having trouble, maybe try this?
[Touch CDMA Windows Mobile ROM Development] incubus26jc:
now i have a big problem. i connected my phone to computer and it came up on phone to connect active sync or file explorer for faster file transfer. i picked file explorer and now my storage card is wiped out. oh no
[Touch CDMA Windows Mobile ROM Development] myn:
How about a new ROM? When's the ETA for v11?
[Touch CDMA Windows Mobile ROM Development] codybear:
Don't let anything write on the card.

Message me and I'll give you a walkthrough to recover everything

along with links to a program to use!!!

BUT IT IS EXTREMELY IMPORTANT NOT TO LET ANYTHING WRITE FILES ONTO THE STORAGE CARD OR IT WILL OVERWRITE ITEMS ON THE CARD AND CAN POTENTIALLY MAKE THE WHOLE THING UN-RECOVERABLE.

I haven't seen much interaction from nfsfan here,

or at the touch pro thread, or his opera for the touch pro thread.

But I had read over at the OpenGL thread here,

that whosdaman said Nfsfan is working on writing another wrapper for a dll.

So is busy with getting that up and running,

and I'm sure he's working on both a new version of the TP rom along with the vogue rom since he has a up and coming changelog for both.
[Touch CDMA Windows Mobile ROM Development] tylers:
Hey guys,

I've been using v10 since its release without issue, but starting this morning it's been freezing up on me at random times. When I got home from work I figured I would just re-flash and the problem would be fixed, but unfortunately every time I either press the soft-reset button (to soft reset/hard reset/bootloader) it freezes, and if I attempt to connect via USB it also freezes.

This is the first issue with a NFSFAN ROM that I haven't been able to sort out on my own, if anyone has any idea's it would be greatly appreciated!

(also since I can't get it into bootloader, I can't flash the rom from my SD card either, already tried...)

Thanks!
[Touch CDMA Windows Mobile ROM Development] incubus26jc:
i went to setting and changed it back to connect using active sync and it made a new storage card 12. all my shortcuts still dont work because its storage card 12 and not just storage card. but everything is still there thank god. should i rename the storage card and take the 12 back off of it?
[Touch CDMA Windows Mobile ROM Development] sci05:
I'm having the same problem, did you find a way to fix this? I didn't see a fix posted. I've done 2 full re-installs and i still have the same problem.
[Touch CDMA Windows Mobile ROM Development] codybear:
yeah, try that,

if it won't let you rename it,

delete the wrong storage card one and then rename.

Same thing happened to me once.

I thought your card got completely corrupted.
[Touch CDMA Windows Mobile ROM Development] derekwilkinson:
Take out the battery, then put it back in. Hold down the camera button, and while you are still holding it, hold down the power button. You should be in bootloader now.
[Touch CDMA Windows Mobile ROM Development] codybear:
you forgot the the stylus in the reset hole part to get into bootloader.

You have to hold down camera and power and press stylus into the reset button.
[Touch CDMA Windows Mobile ROM Development] radar5:
You're looking at two different screens in those pictures. The top one is the current forecast and the bottom one is daily forecast. Note the top picture has the current temperature on the picture while the bottom one only has the high/low and also has the day of the week.

Thanks for the weather fix everyone, worked like a charm!
[Touch CDMA Windows Mobile ROM Development] 4thought:
I never use the stylus to get into bootloader. With the power off, push power & camera at the same time and that gets you into bootloader.
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Yeah, I kinda noticed it was 2 different pictures when I personally had to scroll to get to a pic with the cloudcover posting and how the rest did not have it - as stated in some there is a incomplete cloudcover status in others its not there

It was posted as a response to another user posting a similar issue

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] invario:
You're doing something wrong. You just simply copy the new .MSCR file into the \windows folder and that should be it.

It doesn't really overwrite the file. What happens is that when you copy the file into \windows, your phone knows to look at the new file that you've put there instead of the old one that's contained in the ROM. So it's kind of hiding the old file. If you then delete the .MSCR file, your new file will get deleted, and the old one will still be there (basically, it's now unhidden), just like before.

You're not supposed to be able to delete or modify the ROM file in any way.
[Touch CDMA Windows Mobile ROM Development] Raiden38:
Sorry guys, I don't understand. Whan I copy the file, it ask me if I want to overwrite the file, so I say yes and it tells that it's write protected. I made sure to disable the today screen and reboot.... What did I miss?
[Touch CDMA Windows Mobile ROM Development] Raiden38:
V10.

One of the big issue I have with V10 (beside weather and other related stuff) is the fact that when I want to go in phone mode, I usually click on the green button. But not, it takes maybe 10 times to go phone mode... I did not had this issue with v9. (Well, I had it but it took maybe 2-3 times)

Thx
[Touch CDMA Windows Mobile ROM Development] invario:
Are you using Total Commander? Maybe file explorer works differently.

edit: yes, just checked. this will NOT work with file explorer. you MUST use TC.
[Touch CDMA Windows Mobile ROM Development] tempests:
What phone and radio are you using?

Mine works flawlessly. I hit the green button and get the phone pad.

I'm thinking a lot of problems that are being reported by some are because of an improper Rom Upgrade, some program install after upgrade or a registry tweak.

I suggest anyone upgrading their phone (this has been said before), follow the proven procedure, with no shortcuts, never perform a full restore, use the phone for 24 to 48 hours before adding programs or doing any registry tweaks and then install one program at a time. If there are no issues after the Rom upgrade, then all of a sudden the phone starts acting weird, my above thought would be a logical explanation of the problems.

At least this is the way I see it.
[Touch CDMA Windows Mobile ROM Development] codybear:
See, this right here is proof I'm still a noob.

Didn't know you could go into bootloader with it off.

That's basically what I meant,

you just put it more correctly.

Thanks for this.

Honestly when I did it I still had the titanium activated.

I used Total Commander and

Just copied the script into windows

and overwrote it when it asked.

File Exlporer doesn't allow overwriting of read only files

and system files etcetc.

But I have a theory,

when you disable titanium,

I think it makes it a read only file

(along with all the other attributes, [rom file, etc])

So those that are having trouble copying this over,

try it with titanium still turned on,

and then turn it off and turn it back on after the file to restart it.

Let me know if that works.
[Touch CDMA Windows Mobile ROM Development] incubus26jc:
does any of these touch sensitivity programs work on the vogue?

http://xdaforums.com/showthread.php?t=469865
[Touch CDMA Windows Mobile ROM Development] derekwilkinson:
You don't need to put the stylus in to reset, you can try what I said yourself ;)
[Touch CDMA Windows Mobile ROM Development] 4thought:
Great work NFSFAN. For me, there are two things that would really help the 6.5 ROMs:

1. Adding the volume control that the 6.1 ROMS used

2. Adding a finger-friendly backlight app (I'm using Mylight assigned to the camera button - slow performance though)

My assumption is that including them in the ROM makes them respond faster.
[Touch CDMA Windows Mobile ROM Development] invario:
I use an app called MVBklight. I mapped the "hold camera" button to it.

I've attached the latest version. You have to install both cabs for English.
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
They worked will with his 6.1 ROM's, but I have not tried them on his 6.5 ROM's? Try them out and let us know the results. ;)

Maybe back up your settings first. :)
[Touch CDMA Windows Mobile ROM Development] invario:
Uhm yeah... if you mess up your touch settings, you're kind of SOL. I had to hard reset a few times when I was experimenting using the included Advanced Config app.
[Touch CDMA Windows Mobile ROM Development] commandant83:
i tried the enhanced sensitivity one and it appears to be working on our vogues. unless im on crack its def more sensitive, maybe the experts DD or CB can verify but for now i give it 2 thumbs up.
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
Yeah agreed!! It's always nice to be hooked up to My Mobiler or something similar then you can usually set them up again. Or you use CeRegEditor and back them up as I stated earlier then restore them just in case... :eek:
[Touch CDMA Windows Mobile ROM Development] invario:
you did a soft reset after and it's still working? interesting...

my own experimentation tells me that it should've made things worse:

my starting values after a fresh install of V10 (and V8 also) used to be:

pressure threshold: about 32000

finger pressure: about 4500

LOWERING the finger pressure makes it more sensitive while RAISING the pressure threshold appears to make it more sensitive.

the enhanced version you used sets those values BOTH to 80866.... which would tend to make things less sensitive because of the huge increase in finger pressure.

if you LOWER the threshold too much, YOUR SCREEN WILL STOP WORKING. so one of those CAB files (iTouch_azharsunny.cab, his 'final' version) lowers both values to -1. I'm very wary of trying that, but maybe negative 1 is a special number that makes things super sensitive.

I really don't want to have to hard reset again if my screen stops responding.
[Touch CDMA Windows Mobile ROM Development] invario:
Ooh, you're my hero for mentioning that program. When I first messed up the sensitivity settings, I was searching all over google and I guess I wasn't searching for the right thing, lol. Thanks! :)
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
No problem. Thanks for explaining the settings in your last post!
[Touch CDMA Windows Mobile ROM Development] incubus26jc:
thanks guys. i tried the original cab and it seems to be alot more responsive. at this point im glad i tried it.
[Touch CDMA Windows Mobile ROM Development] invario:
Hmm, now I'm not sure if I'm right. I'm experimenting a lot more now that I don't have to worry about hard resetting (thanks to you)...

edit: yeah, okay, these numbers are confusing me a lot...hmm more testing needed
[Touch CDMA Windows Mobile ROM Development] invario:
hmm veeeeeeeeeeeery interesting! it seems the pressure theshold setting affects how sensitive the screen is to 'points'. the lower the number, the less sensitive it is to small points of pressure (i.e. the stylus!)

i have the threshold set to 5000 and the finger pressure set to 0 at the moment, and the screen barely responds to the stylus at all. i have to press down REALLY hard (so hard that i'm afraid to break the screen now!) with the stylus to get it to respond. HOWEVER, if i use my finger, it's still decently sensitive (feels like it's about stock)

i'm going to bump the threshold back up to around 100,000 and see what happens.
[Touch CDMA Windows Mobile ROM Development] infinateLoopMan:
any luck getting a rom to work? i'm in the same situation. i can get into bootloader but any of the rom's i try to flash is not working. all goes well till the reboot and then it freezes on bootup. either on the bell screen or the htc screen. waited close to an hour. nothing.
[Touch CDMA Windows Mobile ROM Development] invario:
awe, sonofa.... my phone won't unlock now. and it's not because of the sensitivity settings or anything.

i type in my pin, and i hit the unlock button, and it just sits there stuck on the lock screen and does nothing! all the buttons still work, and i can erase the pin number and hit unlock again, but it does nothing!

is this some sort of security feature because i reset the phone a whole bunch of times in the last 10 minutes trying different sensitivity settings? ugggghhhhhh.

edit: yes! thank god... stupid security feature. it let me back in finally.
[Touch CDMA Windows Mobile ROM Development] dufyd:
v11 suggestions:

newer youtube app!

brightness shortcut, please :(

i also liked the orange thing...and the old icons...

just some comments... my phone doesnt ring, it just vibrates...:( ill probably reflash or hard reset...
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
lol, glad to hear you got it working again... :eek: What did you come up with for the values?
[Touch CDMA Windows Mobile ROM Development] codybear:
lmao, 100,000?????? That's just retartedly high.

The higher you have that set the harder your digitizer works.

Meaning you'll eventually overwork it and it'll die on you.

It's like $50-60 US dollars too, plus install.

*5,000 is stock.

*that 0 value is probably why you have to press so hard with your stylus.

Why set it to zero?

I'm reading backwards thru the thread now to see what people have posted lately, maybe someone said it was better, dunno, but I wouldn't recommend a zero.

or going to 100,000.

Shortcuts are easy to make...
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
Did you unlock your phone first? If not look at codybears FAQ

Try getting to the bootloader by turning the phone completely off (hold the power button until a message pops up) and then hold the camera button and press the power button.

I would also recommend you flash back to stock before you flash to V10. :cool:
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
Agreed codybear 100,000 is alittle high... But it is nice to experiment! :D

What are your values set to?

Does anyone know the fix that NSFAN did to improve the response from V9 to V10.

Thanks!
[Touch CDMA Windows Mobile ROM Development] codybear:
yes they do, as you all know by now.

This was actually what I was going to get back in v8 or v9.

and found it after the fact that the sensitivity part was fixed.

lol,

I would assume if it's off, and do what you said it works, but if you do so when it's on, then it won't work. I normally don't turn off the phone to put it into bootloader when I can do it just as easy with the stylus added into the picture. ;)

respond faster? I pretty sure those don't make it respond faster.

Maybe makes it faster for you to adjust things with your finger.

But I think those could make a great addition.

LOL, that sucks.

Finger pressure only affects stuff with touchflo.

IE manilla.

Back in 6.1 when it used touch flo for scrolling,

then you were able to affect that too,

but now it's basically only manilla that's affected by that one.

threshold is the overall pressure used for the rest of the phone.

lol, phm reg edit is included in our phones, and ceregedit is another I use sometimes when messing with registry locations,

but I still prefer total commander for some reason,

don't ask me why but I do. lol.
[Touch CDMA Windows Mobile ROM Development] codybear:
I think he unlocked his phone saying it kept rebooting.

But idk...

And it's more of a requirement instead of a recommendation to flash to stock than flashing v10.

a little high?? that's like empire state building high. lol.

It is nice to experiment,

but that's like overdose level or kill your digitizer level.

I started at the stock level and doubled the value,

(performed a soft-reset inbetween each value change I did)

and then kept adding the stock level to the current level

(ie, started at 5000, double to 10,000 then added 5000 each time)

and just kept adding it till I got it where it responded pretty nicely.

but it was not even 40,000

I don't even think it went above 35,000 to tell you the truth.

But I'm not quite sure and my vogue is completely dead.

I've been focusing on my TP for the past few days, and will be for a week or so till I get everything situated and set up for each flash,

then I can come back to the vogue and revamp the faq,

and will probably make a section or two of the reserved spots I have a vga section, that way I don't have two different ones and can manage everything better.

That is till I get a website or something where I can make it ALOT

easier to navigate and search through everything.

But that prolly won't be for a few months.
[Touch CDMA Windows Mobile ROM Development] 4thought:
The only reason I say that is that installed what I think was the finger volume control that is in 6.1 ROMS to my 6.5. The time it took to load was a lot longer that the one in the 6.1 ROM.
[Touch CDMA Windows Mobile ROM Development] codybear:
Okay, well I think a finger friendly one could be a good addition,

but we do have the volume keys. :p
[Touch CDMA Windows Mobile ROM Development] invario:
CB, both numbers work.

a pressure value of 0 works great. screen is ultra sensitive. between 0 and 200 should work well. strangely enough, i had this value up to as high as 90,000 and the screen still responded okay.

a threshold value of between 30,000-85,000 appears to work well too. at super low threshold values (10000 and less), the screen stops responding to the stylus as well, but still responds to your finger properly. at super hi threshold values (i went up to 1,000,000), the stylus still works but the screen doesn't respond well to your finger anymore.

it's the difference between a pressure 'point' (stylus), and a pressure 'pad' (your finger).

as for what is stock, stock calibration (which is accomplished by doing a screen alignment using the built in software) for both of these numbers were approximately 30,000 to 40,000 for threshold, and 4,500 for pressure. and yes, i do have a thin screen protector film on it.

i settled on 20 for pressure, and 30,000 for threshold and the screen feels great to me.

i have to disagree with you about only one number mattering. both of these numbers matter.
[Touch CDMA Windows Mobile ROM Development] codybear:
I didn't say they didn't matter.

Reread bro.

I said "Finger pressure only affects stuff with touchflo."

The only thing that really uses touchflo now is manilla.

In 6.1 the scrolling used touchflo, but it doesn't anymore.

Therefore, it's really only manilla that uses that key.

Even Nfsfan said so a while back

when we had this same discussion before in this same thread.

This is nothing but a repeat discussion.
[Touch CDMA Windows Mobile ROM Development] invario:
hmm interesting. i could've sworn finger pressure mattered but yeah, you're right. i tested some extreme numbers to see what would happen, no diff.
[Touch CDMA Windows Mobile ROM Development] codybear:
It makes a difference, if you run Manilla, otherwise it has no affect.

But no biggie, you read, experiment, read, contest, read, experiment, and then learn. :D
[Touch CDMA Windows Mobile ROM Development] Jaidon05:
hello guys, I am running into a problem with the titanium weather app. For some reason when it updates I get these red ovals with no temp under it. How can I fix this? Also This rom was by far the best I've put on my Touch.
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Try a search, this was discussed and fixed at approximately page 719

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] kjhadfield:
ok i have a big problem, i hope i can get sum help pls.

this may not be rom related, but i do have sprint on v10 since its release. i havent installed any apps in a couple days. my most recent apps were twoff multiplugi8 1.4. the only other app i been having problems with is galarm, alarm wont go off on time an i dont use a lock app.

i woke up this morn and text my chick, after she reply i try to open text an pgone shut off completly. i had it off on the charger all night. but it shut off like no bat. i try soft reset, but nothing. i get a hold of my car charger an plug it in so a red light turns on, try to turn it on nothing. while its pluged in i took battery out but that red lightstays on, put battery in, wait, nothing. the lights havent changed from red in 30mins. phone ust wont turn on, pls any1 thanks for ur help
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
Agreed codybear!! But it should be more like read, experiment, reflash, read, contest, experiment, reflash, and then learn!!! ;)

And now its time to reflash because I renamed a key in the OEM registry by accident and my phone is acting really funny and slow...:eek: