According to wpcentral (http://www.wpcentral.com/verizon-set-push-out-latest-windows-phone-os-update-htc-trophy), Spark_W's may soon be getting the official 8107 update rom Verizon!
Luckily for us, and with very many thanks to DFT and Mwang, we might be getting a Tango rom around the same time!
Yes, so thankful to DFT and mwang for their work. Although I did a lot of homebrew with WebOS, I recently got a Trophy and installed the custom rom after reviewing the documentation. Really love the options it gives me. Check out Metro Themes. Super cool.
The radio update was huge (the radio file itself is 2MB's larger, but it refuses to flash on my phone atm), but I think it is a lead up to 8107... without a doubt this proves that its on the way.
I don't actually blame Verizon for this delay... I blame HTC. The last two phones getting this update are the Trophy VZW (SparkW), and HTC Arrive (GoldC), the only two CDMA Windows Phone 7's they have in their line up at this time. This is just crappy support on HTC's end, and I hope their "One" policy will eventually help fix this by creating less models and models are are similar to one another.
I hope this fixes some of the other weird texting issues that have popped up when sending SMS via CDMA.
Besides the Radio update of 7720 Mango v3 update, we also got a slightly newer SPL (2.04), not that makes makes a difference to most... this update version number would suggest that the SPL of 2.04 will remain in place.. I'm more interested to see if they will enable Internet Sharing with Verizon's Trophy driver (instead of getting a ported release from GSM Spark... although it works in the cooking universe. )
I do, however, think that a build newer then 8107 might happen. If the CDMA texting issue that people are experiencing is indeed a system issue and not a driver issue, its possible that we will see an ever so slighly newer build of Mango (8110+ perhaps)? It will be interesting to see this update hit and see what it fixes. If the SMS issue is fixed among the other crap that's long overdue, it could be that the long wait is due to Microsoft testing an ever so slightly newer SYS to address these issues... same goes for GoldC users.
I just received a Trophy to replace my Droid Incredible and haven't been able to sync to my Google account. I got it updated using Zune after finding an update was available (even though I JUST got this phone from VZW!) indicating it fixes a Google account sync problem... but alas it also didn't help. I'm on 8107 as I look now, but keep getting a "m.google.com currently unavailable" error (error code: 85010017). Anyone seeing this error or have an idea at what the issue could be? I really need my contacts transferred, thanks guys for any advice!!!??
TheXev said:
The radio update was huge (the radio file itself is 2MB's larger, but it refuses to flash on my phone atm), but I think it is a lead up to 8107... without a doubt this proves that its on the way.
I don't actually blame Verizon for this delay... I blame HTC. The last two phones getting this update are the Trophy VZW (SparkW), and HTC Arrive (GoldC), the only two CDMA Windows Phone 7's they have in their line up at this time. This is just crappy support on HTC's end, and I hope their "One" policy will eventually help fix this by creating less models and models are are similar to one another.
I hope this fixes some of the other weird texting issues that have popped up when sending SMS via CDMA.
Besides the Radio update of 7720 Mango v3 update, we also got a slightly newer SPL (2.04), not that makes makes a difference to most... this update version number would suggest that the SPL of 2.04 will remain in place.. I'm more interested to see if they will enable Internet Sharing with Verizon's Trophy driver (instead of getting a ported release from GSM Spark... although it works in the cooking universe. )
I do, however, think that a build newer then 8107 might happen. If the CDMA texting issue that people are experiencing is indeed a system issue and not a driver issue, its possible that we will see an ever so slighly newer build of Mango (8110+ perhaps)? It will be interesting to see this update hit and see what it fixes. If the SMS issue is fixed among the other crap that's long overdue, it could be that the long wait is due to Microsoft testing an ever so slightly newer SYS to address these issues... same goes for GoldC users.
Click to expand...
Click to collapse
You'd probably read it by now, but from my research it is 8107 and it still doesn't support tethering. I'd guess the issue is they have no way to correctly bill for it, so it's easier for them to just not turn it on at this point.
http://www.theverge.com/2012/4/12/2944147/verizon-htc-trophy-update-rolling-out
There are actually 3 updates that need to be done. 7740, 8107, and the HTC firmware (guessing that's the radio update?)
http://www.ubergizmo.com/2012/04/htc-trophy-8107-update-hits-verizon-wireless/
I would update my phone to this but since it doesn't have tethering I'd rather just flash DFT's ROM.
No, update didn't support tethering. I need to get the official file list captured sometime soon...
Related
Not to give away too much specific information, but I've got a new TMO MDA and the building I am in actually has TMO repeaters. Other TMO phones get perfect reception, and I can even put this new sim into my old unlocked HTC Typhoon and get perfect reception, yet my new TMO MDA won't get any signal.
I'm attempting to scour the registry to find some bit of info or a bit to flip or something of that sort to diagnose the issue. Our TMO rep apparently has RF engineers working on the issue, but if I can fix it sooner than they can I'd be happy.
So, basically, only these new MDAs (other new MDA owners are experiencing the same issue, as well as SDA owners) fail to authenticate to the repeaters in this building. I doubt the repeaters have a list of phones that allow authentication, since the Typhoon was never released by TMO and that can authenticate fine. So I'm thinking there is some bit on the MDAs that is sticking to one band frequency or another, or something to that effect.
Any idea where I could look for info, whether it be a web source or maybe a registry key I could tweak or something of the sort? I got the engineer mode to work (after another registry tweak to turn it on), and it isn't showing any information since the phone isn't connecting to any tower/repeater.
when you go to select networks to use, does the phone give you a list of possible cell networks?
Sorry if i sound obvious....but:
1. Have you compared the Roms on the phones? Maybe the new phone has a different rom which is causing the problem.
2. Have you tried the phone anywhere else outside your building...
3. The engineering mode will still work even without a SIM installed, so if your getting blank information then I think you have an old Rom
Hope this helps
Answers to questions in the thread:
1. If I go to select my networks manually, and it searches for networks, all it finds is the Cingular network, which I can not connect to. It won't find the TMO network at all. But I know it exists because other TMO phones work fine with full reception, and even my old Typhoon works with my new TMO sim in it.
2. The roms on all the MDAs shipped from TMO USA 1.8.10.2 and GSM rom 01.09.10.
3. Phone works entirely fine outside of the building. The building is shielded, but there are repeaters in the building for current TMO users. I know they work since other TMO phones other than the new MDA and SDAs work fine.
4. As for engineering mode... interestingly enough, now that I do have reception (I'm at home right now), I also get blanks. I thought that because I didn't get any reception, I wasn't getting anything from the engineering mode. But interestingly enough, I still don't even though I have reception.
Methinks I do need just the GSM rom. Someone mentioned it in another thread in the Wizard Upgrade forum. Where might I get just that ROM, maybe I'll give it a shot and see if it fixes before doing a full ROM upgrade (which I'd like to do for performance reasons, but I haven't gotten a definitive answer whether I can revert back to bone stone TMO roms with extended roms and everything yet).
I woould suggest getting hold of one of the phones that works, back up the registry, and restore it to the phone that doesn't work. That would tell you if its a registry setting, or a phone/rom problem
britman said:
I woould suggest getting hold of one of the phones that works, back up the registry, and restore it to the phone that doesn't work. That would tell you if its a registry setting, or a phone/rom problem
Click to expand...
Click to collapse
Well, there are no phones that work.
The phones that do work are your run of the mill non-smartphone phones, not a WM5 phone.
Actually, that's not true since my Typhoon is running Windows Mobile 5, but it is entirely different than the MDA.
Only all the stock MDAs shipped from TMO are failing to authenticate to these repeaters. Makes me think that updated the radio rom would help, or something on the repeaters is blocking just these two phones (the Wizard and the Tornado).
Try updating the wizard with one of these roms:
ftp://xda:[email protected]/Wizard/Roms/Tmobile/
Well, I updated the radio rom to 01.12.10...
And still wont connect to these repeaters. The phone seemed snappier to connect when I stepped outside of the building, though. So there is a plus. However, there has to be some reason the repeaters in this building are not allowing my phone to auth.
Does the WM5 version of the Titan (the TELUS model, and some fluke pre-release Sprint devices as well) have the problems people are reporting in WM6?
Examples would be the bluetooth quality bug, and the DirectDraw incompatibility. I'm wondering if something got messed up with the drivers when they went to WM6...
Dishe said:
Does the WM5 version of the Titan (the TELUS model, and some fluke pre-release Sprint devices as well) have the problems people are reporting in WM6?
Examples would be the bluetooth quality bug, and the DirectDraw incompatibility. I'm wondering if something got messed up with the drivers when they went to WM6...
Click to expand...
Click to collapse
Not sure what DirectDraw problems you are mentioning but modal dialog windows always have the SIP button display over them and also from time to time the top menu bar is not drawn and I see another application drawn there instead. Blutooth is fine on my Sprint Mogul. It's a relatively buggy device but I am thinking a lot of that is Windows Mobnile 6 and the first update will fix it. This is my first PocketPC phone and in some ways I regret paying full price to upgrade to it from my Moto Q. Smartphone version of Windows Mobile seems cleaner and more stable.
I'm looking for some advice concerning 3G connection from vodafone in The Nederlands. Right after putting new simcard into my HD I started getting this annoying:
"dialled...
cannot connect for an unknown reason..."
error every time some application tried to get a 3G connection. So decided to put some new cooked ROM based on 6.5. My old one was almost 1 year old and based on 6.1.
So picked up the new Laurentius en voila, it fixed the problem.
Played around a bit with this new rom and decided to check out the XannyTech Grid 1.2.5. Played around with it for one day. Had to soft reset a couple of times cause of HTC messaging that was freezing everytime it tried to read all the txt messages that I restored plus I played around with different tweaks from Advanced Confing etc.
Anyway after all that I soft-reseted for the last time, started up an Opera and bam... connection error again. Exactly as the one before. Did a hard reset, nothing. Same problem all the time.
Anybody experienced something similar ? What do you think it could be ? Should I upgrade my radio ? My current one is 1.13. I was thinking about upgrading to 1.17 but it's very much dependent on a service provider and place so I'm wondering if there's anybody from Nederlands who could give me advice on that, maybe there's some specific version that is the best for Voda ?
thanks for support
Running vodafone in NL here and have to say im having no problems.
Been running on the 1.14 since it was available and just last week switched to the 1.17 and thats running a bit better than the 1.14.
Also i've been running a lot of roms from this place and never experienced the issue you describe.
Suppose it might be the mix of 1.13 and the rillphone dll's found in the varying roms you tried. Since the radio and rillphone dll need to be compatible and support each others functions this might cause your issues.
So concluding my guess would be to try the 1.17 radio.
Yes, as explained in the Android Thread, Voda NL has trouble with their 3G Network or Internet Connection. http://tweakers.net/nieuws/63198/vodafone-kampt-opnieuw-met-landelijke-storing-datanetwerk.html
What the HELL has this to do with Blackstone ROM development!? Come on.
Please mods, close this.
ok, looks like I should check the voda website next time. I'll upgrade the radio anyway since lots of people say that it works good for them. Thanks for help
motoko said:
ok, looks like I should check the voda website next time.
Click to expand...
Click to collapse
No kidding?
Next topic is about your monthly costs are to high @ Voda?
MOD EDIT
Moved to general discussion forum as not related to rom development
@FallenSpartan
Thank you, I was too fast with my choice of discussion place, will pay more attention next time
@SeniorMembers
Looks like you should get some green tea or a massage, I heard that it helps with stress... but come to think about it I'm not very surprised by your reactions since you're probably dutch...
Dear TS,
Just look at any random dutch techsite or just contact Vodafone...
For example see:
http://tweakers.net/nieuws/63198/vo...et-landelijke-storing-datanetwerk-update.html
Hi
Have a Touch2 T3333 which has ROM version 1.28.401.4 (66092)
I bought it as I wanted a Windows phone originally for complete Exchange sync.
However I'm on the verge of just giving up with it and buying another handset, as it's just so riddled with bugs and problematic.
I thought I'd give it one last go and see if there were any updates for the OS to make it usable.
The HTC website does have an update for it which looks significantly newer, however when I try to download that and put in the S/N of the handset I get told that it isn't suitable. There is no way on there for me to part-patch up to an intermediate version then to that version.
I'm not looking for "tweaks" as such, I just want what's there to work (the weather bits, the active sync, Opera not to crash all the time, not to have to launch IE twice every time, the phone to switch properly between WiFi and 3G, YouTube to detect the network connection properly, Audible Player to sync properly, not to have to take the battery off the back and put it back on about once a week every time it locks up.. the list just goes on..)
I'm not sure if these are general issues with Windows mobile itself which has a kind of beta not-quite-finished feel to it and no version really works properly, or if the update would solve these problems.
As I'm so frustrated with the thing I don't mind all that much if I end up killing it completely and then have to throw it in the bin and go out and get an Android based replacement.
I've read about ROM updates on here and I can see in the Mega - ROM - Hotfix thread there's a ROM "WWE Europe - 1.28.401.4" which I'm guessing is the one to try. But then it appears to simply be the version I already have.
Based on how old the ROM it has appears to be (16/09/2009) how can I get the HTC updated ROM 1.33.110.2 to install (the HTC site badges it "T-Mobile" and I have O2), and would anyone else who has be able to comment on whether it's just that my experience with Windows mobile is so poor and I should persist, or whether I should call it a day and move on? (I can see plenty of people have tried getting hold of Android on this handset....could the new Windows 7 work on it in time...?)
Moved to general as not rom development
The OTA notification said it was to improve device security. I didn't think it was possible to get updates on a carrier unlocked phone that was being used on different carrier (AT&T); does this mean that it came directly from HTC and that they haven't forgotten us?
Here is what my device's software information now shows. (Note: I haven't rooted / S-Off or anything yet & I am using the stock ROM... I'm still learning and a big 'ole chicken! )
- Android 2.3.3
- HTC Sense 2.1
- Baseband 12.57.60.25U_26.10.04.12_M
- Kernel 2.6.35.10-g53a84f9
[email protected]18-2#1
Tues Mar 20 20:51:53 CST 2012
- Build 2.42.666.11 CL192788 release-keys
- Browser WebKit/533.1
I didn't happen to take note of what versions my device had previously, but I'm pretty sure that the Android version hasn't changed at all. Does anything else look different to someone more familiar with what this device originally had? Anyone else get this?
EDIT: Now, I see a sync icon (the circle with the 2 clock-wise arrows) just to the left of the band indicator, which I never had before. Apparently, my device is now syncing with my gmail account, which I hadn't set up to sync, as I never ever use it (initially set it up to sync with a Quantum Windows Phone, but I hated the sync limitations). Hmmm... Whose security was this update for anyway?
I haven't noticed anything else, but then again I haven't thoroughly checked everything yet. Seems that this update may not be the same as the one that Euro users have reported in early May (http://forum.xda-developers.com/showthread.php?t=1646616).
Many thanks, ladies & gents!
Debbie
Interesting, too bad the update didn't include a new radio.