This is what HTC says:
Update for HTC Touch Pro2 for Caller ID Display Release Date: 2009-09-16 Category: Hotfix
This update for the HTC Touch Pro2 lets you, your friends and loved ones become closer, making receiving calls as personal as greeting them in person.
Note:
This update can only be applied to ROM version 1.20.xxx.x, otherwise the update will fail.
SEA: http://www.htc.com/sea/supportDownload.aspx?p_id=250&cat=0&dl_id=674
EUROPE: http://www.htc.com/uk/supportDownload.aspx?p_id=250&cat=0&dl_id=674
Thanks for letting us know!
I wonder what this update really does though. I just installed it. But I don't notice any difference with the incoming-call or in-call screen...
didnt understand what this hotfix is for ? any of you installed the update and can tell me the diffrence you see?
Sorry if this is a dumb question, but when did the 1.20.xxx ROM come out - the latest WWE one I found on the HTC site (or in the XDA wiki) is 1.19.401.1.
Any idea what the 1.20 ROM changed?
Ed
1.20.xxx.x ROMs are not out yet. I'm guessing the first one would be the anticipated official WinMo 6.5 upgrade ROM. They really should just cook this "hotfix" into the ROM since it's not even released yet...
ohyeahar said:
1.20.xxx.x ROMs are not out yet. I'm guessing the first one would be the anticipated official WinMo 6.5 upgrade ROM. They really should just cook this "hotfix" into the ROM since it's not even released yet...
Click to expand...
Click to collapse
Thanks, I wondered whether 1.20 would be the 6.5 ROM.
So were you actually able to install the hotfix, if you're still running on a 1.19.xxx.x ROM?
In any case, I think I can hold off until 6th October before worrying about CallerID!
Ed
this at least means 3 things
1) that winmo 6.5 is coming out... sooon!
2) that they are already ready with the new ROM update but are sitting on it till October 6th.
3) that they are plain lazy to incorporate the patch into the update in the days between today and October 6th..
very weird things are happening at htc... can't 1.20 be a new rom BEFORE wm 6.5 comes??
i am on sprint tp2. When I go to settings>Device Information>ROM Version..1.21.......
This mean I have newer version..Or What.
I am on a WWE 1.91.xxxx ROM but the hotfix installed anyway.. And I can't find any difference either.
Tmous - rom: 1.20.531.4
ohyeahar said:
1.20.xxx.x ROMs are not out yet. I'm guessing the first one would be the anticipated official WinMo 6.5 upgrade ROM. They really should just cook this "hotfix" into the ROM since it's not even released yet...
Click to expand...
Click to collapse
The ROM on the T-Mobile version is 1.20.531.4 [51986] WWE.
still dont know
well we still do not know what this fix is for?? anybody knows??
cant see any changes in caller id??
My Verizon TP2 has a ROM date of 8/15/09 and a version number of 1.18.605.12.
I imagine that the versions are carrier specific. 1.18xxxx could be the latest version for VZW and 1.19 might be the latest version for some other carrier.
Right?
-Frank
Hopefull....
I've got a tmobile tp2 and it is a stock ROM dated June18, 2009. It is 1.20.531.4
I'll install this later today and reply back about whether i notice any difference. I'm hoping that this will fix voice command. currently (on my device) it does not announce caller ID info though the speaker or through bluetooth.
My old TP (AT&T Fuze with ROMeOS rom running on tmobile) would announce the name of the caller (or the number if they weren't in my phone as a contact). Then I wouldn't have to pull out my phone to see who was calling.
I hope this fixes that. I'll install it on my drive into work.
I'll let you know if fixes the MSVC bug.
Dissapointed
See my previous post above for my device/ROM info.
It didn't change anything with Voice Command announcing caller ID.
If after a soft reset if fixes anything, i'll post again. I didn't notice anything different at all.
Voice Command Caller ID
how do I set voice command with caller ID in tp2? Is that function available??
shemeri said:
how do I set voice command with caller ID in tp2? Is that function available??
Click to expand...
Click to collapse
I've searched for the answer to that question and came up with nothing. I can't imagine why, since the running gear is not that different from the regular TP (and that worked for me in the past). I think there was even a problem with that one, but a fix was developed and released here.
I'm assuming you are wondering why the phone will not announce the caller ID info (either in you bluetooth headset, or out of the speaker of the TP2 itself). It should speak the number that is calling, or the name if they are already in your contact list. If anyone finds the fix for this bug, please post it in this thread, so that we can be informed of it.
Settings>Voice Command
Make sure Phone is checked & under Options set it to announce incoming calls.
xnifex said:
Settings>Voice Command
Make sure Phone is checked & under Options set it to announce incoming calls.
Click to expand...
Click to collapse
"Phone" is checked in the settings.
If I touch the options button, all I get is "Announce calendar reminders" and it is checked.
I'm running v1.6.21.21051 that came with my tmobile branded TP2.
I also have a Sprint Touch (HTC Vogue) running v1.6.19209. I have the settings set identical in both phones, but the TP2 won't announce calls with MS Voice Command.
I love MSVC, so I hope i find a version that works... or a fix...
Related
Hey guys. Just got a PDF that says 28 February 2005 XDAIIs Upgrade INstructions. & release notes.
ROM version 1.31.139
Radio version 1.06
Think we get it on CD on the 28th!! Can't wait. hopefully fix a few bugs!!
Can I ask where you got the PDF?
Also, do you know how its going to be despatched?
Cheers
Blackberry
Does the XDAIIs upgrade include a Blackberry client?
delete
Just thingking you might want to share that pdf file with us. Upload it, please......
ditto
Hi
Aye, ditto on the upload request please!! Not seen anything on O2's website, my xda or sourceo2. I sure hope they intend to make it available as a download on the same date rather than keep non corporate users waiting.
Nigel
delete
Hi
I assume that they mean the help+faq section and theres nought in there currently. Cant find anything on source o2 either. The XDAIIs launch rom has been in the wrong place on sourceo2 for over 2 months !!!! (they uploaded the wrong rom at first - XDAII launch rom - and hosed loads of peoples IIs machines)
Silly buggers
Nigel
According to Tekguru it is not out until March 1st but will be in production units from next week
Hmmm.. Wonder why the radio version is 1.06 but not 1.06.02
I Got my IIs last week and it come shipped with this rom already
didnt think to check it, been messin with it that much lol
here is the updated bluetoth patch for all to share, sorted out my probs with bt200 headset
Bit disappointing that the BT build is still 3500, they sent that to us bout a month ago & it fixed next to nothing.
We've even made them pay for a couple of car kits to be replaced when the "compatible bt products" list proved to be garbage.
The most annoying thing for me is still the mic level/quality with the phone, this is obviously software related as it works ok with voice recording, skype & even works better wen on speakerphone. Any sign of this improving?
iggywig said:
ok here it is.. Not sure of the legality but what the hey...
Click to expand...
Click to collapse
tried to download the pdf file (Xda_IIs_131139_upgrade.pdf), but nothing happen. how can i download this file?
Evening ladies and gents!
Right, I'm this close to buying a 2s, but what is the liklihood of it ever geeting Blackberry connect?
I'm stunned by the short sightedness of o2 in this respect. It is the perfect device to use as a BB replacement, but the put the client on the xda II instead?
Smartner/xmail whatever just aren't viable alternatives I'm afraid, and I suspect that this will be the case for many people.
Cheers
Looks like O2 now have the thing on their upgrade web site. And two days early as well! Go grab it all from here.
No mention of Blackberry though. Only major update is for bluetooth.
True, but given the crappy quality of my HS850's connection I am hopping this will be the biz for my use, at least.
Strange Rom used in Singapore
My Singapore IIs has the below rom. Does anyone know why the ExtROM Version of my current rom is "newer" then the lastest update from O2? Is there is huge difference between Radio Ver. 1.02 and 1.06? Thank you so much if anyone is know enought to help.
ROM Ver:1.31.00WWE
ROM DATE:12/13/04
Radio Version:1.02.00
Protocol Version:1337.32
ExtROM Version:1.31.920WWE
Hmmm, I tried applying the update. Now the O2 Icon is over in the right of the screen and I cannot pull down the list of connections when I tap on it. Anyone know of a way to move it back to the old position?
Hi,
i have an s620 from HTC itself,
so looking for WM6 , i directly called the manufacture dept. here back in belgium,
and asked info about it.
The friendly person told me there, that there is NO WM6 available on the moment,
and the update of TMOBILE is just a software fix for WM5...
He was going to mail me as soon they finished the software writing, and really release it.
So i could get the direct update from there website.
Now, does it means, that you guys all are using a different cell then me, or that you guys are using a beta WM6?
thanks for clearing out this
We actually have WM6. It is branded by T-Mobile though. You will receive HTC's branded version when they finish "writing it"
http://www.europe.htc.com/support/software/htcs620.html
thanks,
but i got mad of it, did not understand it completly,
And because tmobile buys with htc, so it is strange, why would tmobile have a fanished software before HTC:s
Anyway,
Is it safe to upgrade it with the Tmobile software?
would it be possible, to upgrade it afterwards to HTC software?
I have without any problems.
rklosinski said:
I have without any problems.
Click to expand...
Click to collapse
Hi how did you upgrade it? Did the installer go through by itself?
hi ,
i havent done it yet, but i downloaded an installer from the web (tmobile)
and it seems to be you install it like an other program with active sync,
so it will run it by his self,
But is possible to that if htc launches his software to update it to there, cause i dont like to have all those tmobile logos and things
guys,
when I moved from WM5 to WM6 (both official ROMs), my device ID appeared to change (assumption by virtue of the fact it changed in TomTom 6).
Can anyone else confirm they have seen this? I'm still waiting for HTC UK support to contact me. ABout a week now.
I thought it might be helpful to see who has seen this (regardless of ROM details).
Hi,
Yes, all time you Flash your PPC with new Rom, Your Device ID change, and Tomtom need to be change too (Trafic, SN, etc...)
If you have Tomtom Trafic option, go to tomtom site to change your device id, it's work fine.
As far as I know, it is only the DOPOD, and DOPOD based ROMs that have this problem, and it is a bug in the firmware. The very latest DOPOD release has apparently fixed it- so Mun's Indigo Full which uses the latest ROM is OK, but Lite shows the problem.
Device ID's are a complex matter. Some are based on the IMEI, some derived from the ROM version and some by other means. TomTom and Mobipocket both use 'other means' to derive the Device Code, and it is only with the 'faulty' ROMs that the Device Code changes.
I've taken my Trinity through about 7 ROM updates, and the TomTom Device Code remained the same except in the DOPOD WM6 ROMs; reverting to another ROM resulted in the Device Code going back to what it should be.
This is a real problem for TomTom users because they are currently refusing to relink the new Device Code to the Traffic and Weather account, even if you succeed in obtaining a new activation code. So you have a situation where the software is working fine, but you can't access your TomTom Home subscriptions. Customer Support are now asking for 'proof of purchase' of the WM6 ROM upgrade, which of course can't be provided as there is no 'proof of purchase' for most ROMs.
We have had quite a long topic on this on 4Winmobile, and the latest situation is that it could be a case for Trading Standards to investigate, as TomTom are effectively blocking users from accessing services they have paid for.
hi Neil,
that's most interesting feedback, thanks.
I too have installed at least 6 ROMs on my Trinity. From the OEM Orange UK WM5 (the phone came with) through to mUns TE and others the device code remained static.
Then when I went to the officical Dopod WM6 ROM it changed. I believe I also used the latest official of their ROMS the other week, which was rumoured to fix this issue, but it has not. I think people are confusing the other issue of changing with each hard reset- which I do not have the problem of.
I'm very frustrated with TomTom- it's a month now with no Traffic- and I use it for my work driving the length of the country.
I've suggested that it shouldn't be my problem- after all I have paid the subscription, and it's an official ROM. OK it costs them time to make a change- but it costs them more to keep sending emails to-and-fro asking me for proof etc etc. I've wasted hours on this chasing, HTC (Dopod), Microsoft and TomTom, plus investigating on the web. It's clearly an issue, but no-one will hold their hands up.
If someone could post a link to the latest Dopod ROM which definitively does not change the ID I'd be eternally grateful. And by definitive, I'd prefer first hand experience ;-)
folks,
tonight I bit the bullet and installed mUn's Indigo Full. Very quick to install, nice looking ROM but the Device ID has still changed :-(
So every Dopod official ROM and now the full Indigo changes the device ID from the original WM5 ROM and every other WM6 ROM.
I've tried 3 ROM in 7 days now. This is getting silly!
I think I will not be renewing my TomTom Traffic. Oh and I forgot to say, HTC Europe sent me a fob- off email tonight.
"Contact your phone supplier......" Thanks. They seem to be deliberately avoiding this- I gave them the chance to just say "yes" we know there is an issue. That would be enough for TomTom.....
TomTom and license key
I have heard that TomTom only allows the use of the license key twice. Has anyone found this to be true? Because, if so, a lot of people who have installed WM6 on their Trinity and have been asked to activate Navigator again (myself included) will have to think twice before switching ROMs again.
Hmm I'm not sure if this is correct- if the map is activated, and you change the device ROM, TomTom does not need the map to be reactivated normally.
This ONLY happens if you change the device ID- i.e. you then need to reactivate with the licence.
If Device ID's change again then yes there is a problem.
Please lets not confuse the issue here- the problem is for Traffic subscriptions- you can only change your device in the TomTom account online once in 6 months.
After this you must go through TomTom support.
It's not got customer service to be waiting 1 month with no resolution.
sickboy555 said:
Hmm I'm not sure if this is correct- if the map is activated, and you change the device ROM, TomTom does not need the map to be reactivated normally.
This ONLY happens if you change the device ID- i.e. you then need to reactivate with the licence.
If Device ID's change again then yes there is a problem.
Please lets not confuse the issue here- the problem is for Traffic subscriptions- you can only change your device in the TomTom account online once in 6 months.
After this you must go through TomTom support.
It's not got customer service to be waiting 1 month with no resolution.
Click to expand...
Click to collapse
I also had the "famous" devide-id change after upgrading to the official WM6. But in my case something very strange: I DID send a proove of repair to TomTom (I really had a repair) and then TomTom DID reset my device-id to the correct device-id (when I actually look at the TomTom-site my settings are all correct).
But now I still get an error using traffic (and other Plus-services). I resettet my device on the TomTom site many times but no effect.
The situation now is that I have alle the correct codes, can use TomTom (6) but still can't use traffic!
When I go back to an unofficial ROM (p.e. Sleuth 3.2) with another device-id everything's ok.
Frustrating... don't know what to do anymore, TomTom did their job.
oh no Pietrucci, that's bad news. And very odd if they changed the ID, but going back to another ROM with old ID, Traffic works.
So if TomTom update my device ID and Traffic still doesn't work I'm scuppered.
Apparently they never let you go back to an old ID in your account, which means going back to an old ROM may not help either. Maybe there is something wrong with their account system for Traffic, if your old one still works???
pietrucci said:
I also had the "famous" devide-id change after upgrading to the official WM6. But in my case something very strange: I DID send a proove of repair to TomTom (I really had a repair) and then TomTom DID reset my device-id to the correct device-id (when I actually look at the TomTom-site my settings are all correct).
But now I still get an error using traffic (and other Plus-services). I resettet my device on the TomTom site many times but no effect.
The situation now is that I have alle the correct codes, can use TomTom (6) but still can't use traffic!
When I go back to an unofficial ROM (p.e. Sleuth 3.2) with another device-id everything's ok.
Frustrating... don't know what to do anymore, TomTom did their job.
Click to expand...
Click to collapse
I have exactly the same problem. Online my plus services shows that the TomTom Device ID is correct, BUT traffic still doesn't work.
Going back to the older version of WM6 with the older device code and it works. So TT Plus servers must still have the old device code associated with my PLUS account even though PLUS online is showing the new code.
I've told TT that it's not working but no fix so far.
MAJOR UPDATE: New build of WM6 fixes the device ID change issue. The device ID is the same as in WM5 - the first cooked ROM to include the fixed build is Schap's 3.60a.
Best get onto TT and have that code reverted back sharpish!
hi eaglerest can you post a link to the specific new build of WM6 you are referring to please (the OEM ROm, not the cooked one).
The 8th of August DOPOD rom DOES NOT fix the device ID bug.
i.e. this one RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship
hi,
sorry it's a hermes build.....
http://forum.xda-developers.com/showthread.php?t=322905
ah, so it's not just confined to the Trinity then.
thanks for the info eaglerest.
right, I've given up with this ridiculous Device ID business!
I told TomTom to leave the ID alone (after 6 weeks with no Traffic) and have gone back to mUn's TE, which preserves the old Device ID.
Not what I really wanted but I think I'll be an old man before it gets resolved.
HTC In Asia and Europe fobbed me off and wouldn't even acknowledge this as an "event" let alone a bug.
Hi all, am I missing something? I thought that the latest release of code i.e. OS 5.2.1620 Build 18125.0.4.2 was going to fix this? Or have I mis-read the posts. I ask because I tried the latest Bepe build, and my device ID still changed. Does anybody know excatly why the ID is changing?
moondevil said:
Hi all, am I missing something? I thought that the latest release of code i.e. OS 5.2.1620 Build 18125.0.4.2 was going to fix this? Or have I mis-read the posts. I ask because I tried the latest Bepe build, and my device ID still changed. Does anybody know excatly why the ID is changing?
Click to expand...
Click to collapse
Not really sure what you think you have misread. perhaps you are thinking of a bug whereby the Device ID apparently changed on EACH hard reset? I personally have not seen this.
My problem is that WM5 = DEVICE ID A (My Traffic is registered to this.
mUns TE WM6= DEVICE ID A
Official DOPOD WM6 ROm, Indigo FULL = DEVICE ID B. Now my Traffic will not work.
TomTom will only change the registered device if I can provide proof from HTC or someone else that this is a bug. Guess what- they've been no help at all. Neither have Microsoft or Orange.
sickboy555 said:
Not really sure what you think you have misread. perhaps you are thinking of a bug whereby the Device ID apparently changed on EACH hard reset? I personally have not seen this.
My problem is that WM5 = DEVICE ID A (My Traffic is registered to this.
mUns TE WM6= DEVICE ID A
Official DOPOD WM6 ROm, Indigo FULL = DEVICE ID B. Now my Traffic will not work.
Click to expand...
Click to collapse
OK, just so I'm clear on this because I'm (nervously) about to go down the path of updating for the first time. I'm coming from WM5, having never flashed before, will upgrading with Bepe's latest of .74 change my Device ID or not?
probably, but I have no idea for sure. Not used that ROM.
If you use TomTom Traffic and it does change, you will not be able to use it anymore. If you have never changed your device ID with TomTom, you can do it yourself- but only once per 6 months via your account on their website.
You will have to re-register all your maps too.
If you saw moondevils post, his ID changed with one of bepe's builds. I imagine that bepe uses the same core OS for all his builds so your ID will likely change.
mUns TE is the only Wm6 ROM I have tried which keeps the ID (and I've tried many many).
sickboy555, thanks for your reply.
I *thought* I'd seen something relating to the newer build not changing the ID, but I was obviously mistaken. Like you, I've tried most of the "post Dopod official" Roms and they all change my device ID. I followed the link to the Hermes build and saw that it was a 18125.0.4.2 build, and thought that maybe this would cure it. But obviously not.
What I find funny is that Bepe is building Tomtom in to his builds, and I'd love to use it, except I just upgraded from my SPV M5000 (1 change) and now tomtom won't let me reregister my maps.
Bugger!
hey i was looking at the other forums and they all contain some kind of radio rom thread with many radio roms and its sticky'd so i decided i should make one also so everyone can find radio roms easily and flash them and see which they get the best performance out of!
some radios extracted with thanks to: da_mayhem
T-Mobile WM6 Radio - 4.1.13.34_02.79.90
HTC WM6 WWE ROM - 4.1.13.44_02.94.90
Rogers WM6 Radio - 4,1,13,47_02.98.90
New 4.1.13.51_03.07.90 radio
and finally some VOX radio's I converted over to the Excalibur/Dash
Vox Radio 4.1.13.47_02.98.90
Vox Radio 4.1.13.37_02.83.90
Vox Radio 4.1.13.47_02.94.90
Vox Radio 4.1.13.60_03.18.90
Make sure you have the USPL loaded into your device (Thanks to jockyw2001)
**How to Flash**
1. download the USPL file
2. Run USPL.bat and follow the instructions
3. once your screen turns blank and the USPL.bat application finishes open up the radio rom file you would like to flash and run the RomUpdateUtility.exe file
4. Report your results so others can see!!
***Flash at your own risk and ask questions or read if your uncertain as to what to do***
well ill be the first one to post my results. out of all the radios i believe the 02.98.90 radio gives me the best service in my area
battery life not bad either
im in Woodland Hills CA and using tmobile service
i can say out of the 3 official ones ive used only the rogers one had a decent reception in my area....
I am intrigued with the vox ones... ill have to load one of them up this week and test it.
I was wondering... is any of these radios known to drop calls?
I'll explain myself. I usually call someone and some people will hang up and call back. The fact is that these kind of calls won't usually come through, as they receive the message from the network operator that the terminal is powered off or out of coverage (rough translation).
If they call back once again, this time the call comes in.
Any ideas on what's causing this behaviour?
A similar problem happens when I'm on the data connection chatting with palringo or browsing the web. If someone calls me in these moments the call won't come through.
Bump!
Any ideas on this issue?
Which Radio ROM would you suggest I downgrade to given that now I have 4.1.13.51_03.07.90?
Just wondering, what these radio roms did, and do they affect you having wm6.1/6/5?
Were can I go to see what radio version I have installed on my dash?
stickman said:
Bump!
Any ideas on this issue?
Which Radio ROM would you suggest I downgrade to given that now I have 4.1.13.51_03.07.90?
Click to expand...
Click to collapse
yeah im wondering that to since i get alot of dropped calls now
Well, I think I've narrowed the problem to a provider issue.
I'm on a unlimited data plan and have palringo and exchange server setup so I'm always online.
So, I get the above mentioned behaviour, but it just doesn't happen with the dash. My Nokia E65 does the very same thing, call won't come through sometimes if I'm idling on palringo or pulling mails, so it has to be either that Vodafone has old gsm equipment in my area or that it's misconfigured.
Over 3G the problem goes away, it happens on gsm but not just to the dash so I think I'm done blaming the htc.
i changed it to the new radio and i get perfect reception everywhere now and my last phone call sounded extra clear
BUMP FOR THIS THREAD. it deserves a sticky. I gotta test every radio out of this and see which one works flawlessly with WM6.5
EDIT: The HTC radio has been removed. I wanna use with my non T-Mo network
I have ookba's newest ROM to date on my phone, with the newest radio on there. Only problem is... it DRAINS my battery like no other. If its on standby, it goes down really fast, and I'm at 80% within an hour of zero use. Which radio version here would be good and work well with WM6.5? Which one has good service?
HTC_Phone said:
I have ookba's newest ROM to date on my phone, with the newest radio on there. Only problem is... it DRAINS my battery like no other. If its on standby, it goes down really fast, and I'm at 80% within an hour of zero use. Which radio version here would be good and work well with WM6.5? Which one has good service?
Click to expand...
Click to collapse
You should be careful with this particular rom, ookba stated not so long ago that testing other radios has been not stable with his 6.5 rom.
gmaniac2008 said:
You should be careful with this particular rom, ookba stated not so long ago that testing other radios has been not stable with his 6.5 rom.
Click to expand...
Click to collapse
Hmmm... Alright. Thank You for that. I'll wait and see if anyone else tests it for the 3VO rom.
Hi All,
I looked thru 160 pages of searching with different keywords, and didnt find answer. I have the stock ATT rom, hard spl to add the 4.49 radio, have personalizer and Photo Contacts Pro 5.5 on it. Nothing else except to the two cab fixes to reduce ram useage.
The problem is at times when I get a txt msg and I hit reply the txt opens up and when I slide the phone to expose the keyboard to reply, the phone will freeze up, the cursor is still blinking to input but the buttons and the touch screen is not responsive, I have to hit the reset button on the side of the phone to regain control. Anyone else having this problem and is there a fix for this?
Check the hot fix on HTC's site
I have had the same issues and HTC recomended installing both hotfixes as they fix alot of other isses other than what is shown. I will let you know how they work as I am installing them now.
i have the att tilt 2 and tried to install the hotfix to stop my phone from freezing but when i tried to run the installer its said not compatible for this phone??? what is the deal?
kenyaata said:
i have the att tilt 2 and tried to install the hotfix to stop my phone from freezing but when i tried to run the installer its said not compatible for this phone??? what is the deal?
Click to expand...
Click to collapse
Yep had the same problem when I tried to install the caller ID fix. the sms fix installed fine no issues there. I think the reason why it might have said its incompatible is because it might have been for the WinMo 6.1 not for the 6.5 version. I read somewhere (sorry who said it) that it checks against the loaded rom. and my feeling is the sms fix wasnt corrected in the 6.5 version but the caller id was, possibly. I have Tilt 2 from ATT and it has WinMo 6.5 on it stock, just hardspl-ed it to add the newest radio to it, which is 100x better then the stock version that came with the ATT rom.
The hotfixes only work on the stock ROM. Not sure if the fact that the OP changed the Hard SPL and the radio would prevent the hotfixes from installing. And the stock ROM for the Tilt 2 is WM 6.5, not 6.1.
I know the tilt 2 comes with 6.5 I stated that already but I tried the caller id fix before I hard spl when I had it only couple of days ago and still wouldnt update on the stock att rom with no tinkering.
The hotfixes will work on HardSpled phone as long as rom is original. I did mine when they first came out with no issues.
I also looked a little more closely at this, I installed the rom 1.86.401.0 that comes with the radio 4.49.25.14 and the date of this is new compared to the hotfixes, with that said would it be safe to assume the hot fix is already implimented? Cause ever since I dumped the ATT stock rom and add this htc original rom, and the tweaks I wanted to add, I have had no issues with the phone and have not installed the hotfixes except for the keyboard which seems to have come out after this rom update.
Any word on how we can get it to work on the phone with other roms?? or if I go back to th eoriginal will it work... I am basically stuck in limbo every time i go into sms now and i am about to drop kick the phone.