Database Users

Vzw - mr2 rom?

Has anyone tried MR2?
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless

I think something in the update locks out the aGPS fix. But I don't know much else. I have had to tell people to downgrade to get the gps to work after going to MR2.

drewcam888 said:
I think something in the update locks out the aGPS fix. But I don't know much else. I have had to tell people to downgrade to get the gps to work after going to MR2.
Click to expand...
Click to collapse
hmmmmm, interesting. I would kill to ge the Titan back so I can see what this thing is all about.
From what I have read, they are going to lockdown aGPS and open up regular GPS.

edit: wrong post

I wish someone is brave enough to download MR2. I like MR1 and installing the Valhalla cab was simple. Wondering if I can do the same with MR2.
edit: Looks like the cab does not work with MR2
http://forum.xda-developers.com/showthread.php?t=424387&page=49

Verizon updates mostly restrict the phone. Some have tried the MR2 update and say it kills the agps. So just stay with MR1 or go custom.

MR2 works with aGPS as long as you use GC's fix, however, you will not have internet sharing, and other options. I would use DCD 3.2.6

i've downloaded and used MR2 and everything stills works Vahalla Server, google maps, live search aMAZE GPS, internet sharing, wifiRouter, etc.

I just got a replacement phone because of reception problems, and it has MR2 preinstalled. Also everything I have installed as post above, works fine...
I asked tech support about it and they said they didn't know the differences from MR1. That was the answer I expected.... They also said there will be another update real soon called MR3. Although real soon in verizon language could be 6 months
I wonder what this is all about?

I kinda doubt a MR3 update since they stopped selling the xv6800

Is the GPS locked on the Verizon Touch 6900?

Hi y'all,
I have a 16 month old Verizon Touch. When I had the "in the wild" 6.1 Windows Mobile I was able to do the Valhalla GPS Fix and got the GPS working just great. But the official ROM got released and like an idiot I flashed the MR1 official ROM. And then I lost the GPS. Valhalla does not work, QuickGPS does not work.
My only recourse is: I complained enough so I got an early "New Every Two" so when the new Whitestone/Imagio comes out on October 6th I plan to ditch my Touch for good and go with the new phone.
I have my data on block on the Touch because no sense in paying $30 a month without GPS to assist Google and Windows Live. I also bought a lovely new GPS program called CoPilot Live 8, which is extremely reasonably priced, but I'll have to wait until I buy the Imagio to run the thing. Though, I can get maps of any particular area with the program, just can't create a route to a destination without GPS.
So I'm just wondering, anyone else with a Verizon Touch struggling with the GPS on their phone? Tech support swears they don't lock out the GPS, they say its Google's fault for not accessing the GPS on the phone...yeah, sure.
Bye, R

DrRoger said:
Hi y'all,
I have a 16 month old Verizon Touch. When I had the "in the wild" 6.1 Windows Mobile I was able to do the Valhalla GPS Fix and got the GPS working just great. But the official ROM got released and like an idiot I flashed the MR1 official ROM. And then I lost the GPS. Valhalla does not work, QuickGPS does not work.
My only recourse is: I complained enough so I got an early "New Every Two" so when the new Whitestone/Imagio comes out on October 6th I plan to ditch my Touch for good and go with the new phone.
I have my data on block on the Touch because no sense in paying $30 a month without GPS to assist Google and Windows Live. I also bought a lovely new GPS program called CoPilot Live 8, which is extremely reasonably priced, but I'll have to wait until I buy the Imagio to run the thing. Though, I can get maps of any particular area with the program, just can't create a route to a destination without GPS.
So I'm just wondering, anyone else with a Verizon Touch struggling with the GPS on their phone? Tech support swears they don't lock out the GPS, they say its Google's fault for not accessing the GPS on the phone...yeah, sure.
Bye, R
Click to expand...
Click to collapse
It does seem that VZW does lock the GPS. Not letting customizations run, unlocking, & Flashing a custom ROM will unlock the GPS.
There are plenty of threads on this subject.

jadesse said:
It does seem that VZW does lock the GPS. Not letting customizations run, unlocking, & Flashing a custom ROM will unlock the GPS.
There are plenty of threads on this subject.
Click to expand...
Click to collapse
yea there are lots of theads in the vogue upgrading thread. pretty much your going to have to downgrade your radio to a pre gps one and then reflash a gps enabled rom and not let customizations run.

DrRoger said:
Hi y'all,
I have a 16 month old Verizon Touch. When I had the "in the wild" 6.1 Windows Mobile I was able to do the Valhalla GPS Fix and got the GPS working just great. But the official ROM got released and like an idiot I flashed the MR1 official ROM. And then I lost the GPS. Valhalla does not work, QuickGPS does not work.
My only recourse is: I complained enough so I got an early "New Every Two" so when the new Whitestone/Imagio comes out on October 6th I plan to ditch my Touch for good and go with the new phone.
I have my data on block on the Touch because no sense in paying $30 a month without GPS to assist Google and Windows Live. I also bought a lovely new GPS program called CoPilot Live 8, which is extremely reasonably priced, but I'll have to wait until I buy the Imagio to run the thing. Though, I can get maps of any particular area with the program, just can't create a route to a destination without GPS.
So I'm just wondering, anyone else with a Verizon Touch struggling with the GPS on their phone? Tech support swears they don't lock out the GPS, they say its Google's fault for not accessing the GPS on the phone...yeah, sure.
Bye, R
Click to expand...
Click to collapse
Hey DrRoger-
I remember you from Hofo, we got our xv6900's around the same time.
Like you, I had the GPS working with 6.1 update and Valhalla then lost it by letting the customizations run on the official ROM.
I just got my GPS working again today by following the instructions here: http://forum.xda-developers.com/showthread.php?t=533639
It is a bit of work and a lot of flashing but it does work. I think I was brave enough to go through all of it because I plan on getting the Touch Pro 2 (or something better if it comes out) when my NE2 is up in a couple of months. If you decide to try it just follow the instructions precisely, remove your storage card before unlocking and use a computer with xp on it and it should be a fairly smooth process.
Good Luck!

http://forum.xda-developers.com/showthread.php?t=533639

I have flashed my Vx 6900 and I thought my GPS has been unlocked. But it keeps trying starting up in GPS test. And I found my GPS working in COM4, 4800b/s.
Could everything help?
Thanks

damiloveu said:
I have flashed my Vx 6900 and I thought my GPS has been unlocked. But it keeps trying starting up in GPS test. And I found my GPS working in COM4, 4800b/s.
Could everything help?
Thanks
Click to expand...
Click to collapse
Make sure your location services are turned on. Start > Settings > Phone > Services > Location Settings
It's off by default.

vzw locks
Yeah vzw locks gps but it is a cat and mouse game with the locks and unlocks. Vzw wants to milk you (or others) for their vz navistupid (ie navigator) and charge you for what should be free. They have done this for years. At one time you had to pay verizon for the pictures you took on your phone. When the removable media came std on phones they lost that revenue squeeze.
They will continue to lock out technology to milk the $ out of it. Eventually they have to free it cause they will loose customers. A vzw rep told me this weekend that vzw is going to release their lock on gps in the "near future".

imdarkside said:
Yeah vzw locks gps but it is a cat and mouse game with the locks and unlocks. Vzw wants to milk you (or others) for their vz navistupid (ie navigator) and charge you for what should be free. They have done this for years. At one time you had to pay verizon for the pictures you took on your phone. When the removable media came std on phones they lost that revenue squeeze.
They will continue to lock out technology to milk the $ out of it. Eventually they have to free it cause they will loose customers. A vzw rep told me this weekend that vzw is going to release their lock on gps in the "near future".
Click to expand...
Click to collapse
Well VZW has been in a lot of trouble over that. And actually, if you get a world phone now from VZW, the GPS is supposed to be unlocked. I know that doesn't help you guys with Vogues, but it's a start. On the other hand, you can visit the Vogue upgrading section and hit up some of the forums just for unlocking your gps radio. Or even change to a custom ROM. I've been using NFSFAN's Windows Mobile 6.5 Roms with great satisfaction.

I followed the previously linked instructions a few month ago on my 6900, and installed NFSFAN's 6.5 build. Has been working great with a working GPS since then.

[GPS/AGPS] REAL solution analysis thread (Jupiter Tweaks) - v006! - Froyo JI6

Here's that donate button you guys were looking for. >_>
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7ELH2CPLUZLQY
ANECDOTAL EVIDENCE IS NOT REAL EVIDENCE!!!
Get My Tracks from Google Market and post your GPS trip.
My first Froyo 2.2 test:
http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=108472444080796738089.000491a2c10ac25693114
Jupiter.XML
Jupiter.XML is not a Samsung specific file.
Jupiter mods
I've been modifying some information from the Jupiter XML to get different results. After installing a new jupiter.XML, got to LBSTestMode and select Delete GPS Data.
They can be installed by:
Code:
adb push jupiter.xml /system/etc/jupiter.xml
or (if permission denied)
adb push jupiter.xml /sdcard/jupiter.xml
adb shell
su
busybox cp /sdcard/jupiter.xml /system/etc/jupiter.xml
rm /sdcard/jupiter.xml
I made some changes to Jupiter (hopefully) enabled low noise amplification and remove a lag while trying to regain a hot fix.
View attachment Jupiter-v001.zip
Here's a v002 without ANY AGPS data. Because of a theory that AGPS is causing inaccuracy problems, I've disabled it completely. The fix will take longer, but maybe it'll be more accurate. With AGPS off, you won't get signal indoors. Remember that please and this is for the sake of testing.
AGPS doesn't have anything to do with accuracy. Stick with v001
Removed
You should also disable AGPS within Android
You can disable AGPS this way
Code:
adb shell
su
cd /dbdata/databases/com.android.providers.settings
sqlite3 settings.db
update secure set value="0" where name = "assisted_gps_enabled";
.quit
reboot
v003 has AGPS again. Make sure you enable AGPS in android provider settings (see above). I also switched the SUPL to supl.google.com:7576 instead of spirent. I changed the FrqPlan to match the Blackberry devices FrqPlan.
View attachment Jupiter-v003.zip
v004 is based on XWJP4 from a i9000 build.
I changed a lot. I made my changes to jupiter.xml (disabled the LNA for testing) and I'm using unstable 300ppb (even though I think ppb are meaningless since ppm are more important). It has LBS data enabled from this firmware. Also, I put the new drivers and forced SUPL to supl.google.com in both jupiter and gps.conf
pulled for more testing
v005 are tweaks from XWJP4. I couldn't get the new libgps.so to work on our Captivates (crashes on boot). gps.conf goes in (/system)/etc
View attachment Jupiter-v005.zip
v006 is JI6 compatible. JI6 (the Froyo build) uses the same GPS driver structure as i9000 XWJP4, so we might be able to swap files. This also means it's compatible with i9000 devices. This is mostly playing with SUPL to point to Google and remove a possible fix lag.
/system/etc/jupiter.xml
/system/etc/gps.conf
/data/gps/secgps.conf
View attachment Jupiter-v006.zip
Jupiter Research
It's a interface configuration file for GLGPS from Broadcom. If Samsung messed up, IT'S HERE
These are Samsung's settings (with OH7 OTA)
LogPriMask="LOG_DEBUG"
LogFacMask="LOG_GLLAPI | LOG_DEVIA | LOG_NMEA | LOG_RAWDATA | LOG_DEVMS | LOG_ASIC_IO | LOG_BBTEST | LOG_DEVET | LOG_MESM | LOG_DEVKF | LOG_DEVJG | LOG_DEVMR"
FrqPlan="FRQ_PLAN_26MHZ_2PPM_26MHZ_300PPB_UNSTABLE"
RfType="GL_RF_4751_DANUBE"
BrcmRFwildBase="0x1E2D6409"
BrcmRFclkDiv="21"
BrcmRFclkRefHz="26000000"
pps-enable="false"
pps-offset-ms="0"
pps-width-ns="100"
THIS IS WHAT WE SHOULD PLAY WITH!
I'm done some research and these are values for FrqPlan:
The TCXO has to be accurate +/- 2.0 ppm.
The number after FRQ_PLAN_ describes the type of TCXO used, for example,
FRQ_PLAN_13MHZ_2PPM is a 13MHz reference clock.
FRQ_PLAN_13MHZ_2PPM
FRQ_PLAN_16_8MHZ_2PPM
FRQ_PLAN_26MHZ_2PPM
FRQ_PLAN_10MHZ_2PPM_10MHZ_50PPB
FRQ_PLAN_20000_2PPM_13MHZ_50PPB
FRQ_PLAN_27456_2PPM_26MHZ_50PPB
FRQ_PLAN_33600_2PPM_26MHZ_50PPB
FRQ_PLAN_19200_2PPM_26MHZ_100PPB
RfType values:
GL_RF_PALS7
GL_RF_BARRACUDA
GL_RF_2075_LN22
GL_RF_2075_BRCM
GL_RF_PALS7_BRCM
GL_RF_BARRACUDA_BRCM
GL_RF_BARRACUDA_EXT_LNA
I found this info here:
http://openembed.com/files/pdk15_imx35__Linux_RM.pdf
Captivate Settings from OTA OH7:
Code:
I stripped everything else because we don't need it. We're not debugging. In fact, that might be a reason for the lag (all that unnecessary debugging).
This is the HTC Legend's XML file
Code:
See a difference? NO debugging and different FRQPlan (different chip anyway)
I FOUND SOMETHING WORTHWHILE!!!
Blackberry device that uses the same chip. Here are the settings for gl1
Code:
Blah blah blah! Re-education part
I think a lot of you are playing with options, not knowing what you're doing. I've written some GPS applications for WinMo (check my post history) and have taken a look at this issue. I'm currently working on a project that uses the GPS and Android phones. I negotiated a deal with AT&T to get 50 Samsung Captivates (@ $150 each) with 2GB/mo ($25/mo) for a client and I think I'm going to cancel that.
I don't think many of you understand what's going on with the phone or what AGPS does. AGPS is basically GPS support with cell towers. There are different levels of cell tower support.
MS-Based usually just uses the cell tower's location (not yours) to figure out where you are. This will allow you to go online, and get the cell tower number and find out it's GPS location. From there, the GPS using satellite charting data to find and keep a fix. GPS almanac data (says where the satellites are in the sky) can be supplied by the cell tower (the point of MS-Based), downloaded over the internet or downloaded from GPS signals (the last of the 3 being the slowest). Getting a fix without having any satellite data or positioning is known as a cold fix.
MS-Assisted does what you guys would already figure is happening. It uses the cell tower positioning and cell tower signal central to triangulate your position. In WinMo this would disable your data connection but it seems that's not the case in Android. Regardless it might slow down your internet. Obviously the accuracy here is poor.
SUPL just tells you the lat/long position of the cell towers so changing servers does nearly nothing. Google may have faster SUPL servers than spirent but the data should be the same. Once you have that data, it should be cached locally (but who knows, this is Samsung we're talking about.)
The problem is, technically speaking, the GPS should work even without AGPS. I have a couple of GPS devices with SIRFIII and it works beautifully, no AGPS needed. It should be able to download the almanac, ephemeris and time from the GPS satellites without any cell towers. That's how you know the issue isn't your settings.
Disable AGPS and you'll realize you have no options to play with. You're all playing with AGPS settings which aren't really hardware based GPS (and thus inaccurate). AGPS is not accurate. It was never meant to replace hardware GPS (which is why they put hardware GPS in phones). Hardware GPS has much more accuracy but the fact is, hardware GPS is NOT working on the Samsung Captivate. That's the baseline problem. Forget your AGPS settings. AGPS should only help you with almanac data and getting faster fixes but after that it should be running on standalone hardware and only fall back to the inaccurate AGPS when you lose a clear view of the sky (like when you're in a tunnel).
I notice little issue when I'm standing still. It's when I'm moving that the accuracy dies. With further investigation, it seems the GPS literally stops updating the location after a couple of seconds. You don't notice if you're standing still since you're in the same spot, but when you're driving you'll see it. The GPS freezes for about 20 to 30 seconds.
The question is: Why is it not working?
Here are my hypotheses.
1) There's a function running that borks the GPS and makes the GPS driver crash or lag. The GPS driver quietly reboots and then it gets a fix. This could be the reason why, after disabling and enabling GPS, it grabs a hot-started fix of a location it was struggling to get before. You manually reset the GPS driver. I've tested it with Google Maps/Navigation. The GPS doesn't move for 30 seconds. It freezes, but when I close (disable GPS) and open the app (enable GPS) it gets a hot started fix in 5 seconds. Had I not disabled and enabled the GPS, it would have lagged there. This could be a software issue.
2) The GPS isn't using the almanac data. The almanac data says where the GPS satellites are now and where they will be. The GPS uses this to track. If this isn't used, it needs to get a fix again every so often.
3) Cell towers are actually messing you up because their times are desynchronized or almanac data is outdated. (and we all would love to blame AT&T)
As for my project, I'm ready to change my order from 50 Captivates to 50 Xperia X10 phone. The X10 actually has a WORKING GPS (meaning my app works fine and isn't the cause). I have both phones that AT&T gave me to develop my application. I wis

Thank you for the info. I am eagerly awaiting a true fix

makes sense, let us know of your future findings

I just want to say this is an excellent post and very informative. Thanks for writing it. Unfortunately, I'm seriously debating returning my Captivate over this whole fiasco. The OTA hotfix that's pushing out today does nothing to fix this issue and I some how doubt this will be resolved any time soon.

There are two test ROMS that were leaked, JH2 and JH3, that already have GPS logging enabled by default. We've been turning it off since the data isn't useful to us and it fills up the phone's storage quickly. Would those logs be useful to you?

I have a Captivate, so I don't need the logs really. What are your experiences with Dynamic Accuracy off? I feel like that could be the issue. I know the GPS disables after 120 seconds with Dynamic Accuracy off, but when it does work, how well does it work for you guys?
Also, is the GPS issue for ALL Galaxy S devices? (Vibrant/Captivate/i9000)

I just got my captivate so i havent been around long, but i know for sure it affects all the US versions of the Galaxy S series (Fascinate, epic 4g, captivate, vibrant), im not sure about the European i9000

It affects all Galaxy S phones regardless where you bought them. And the issue is with BroadCom (the GPS chip maker). There is a faulty driver and/or faulty chip firmware. From what I gather, BroadCOM gave Samsung the updated driver at the end of the August which our latest JH7 probably doesn't have.

faspalma said:
I just want to say this is an excellent post and very informative. Thanks for writing it. Unfortunately, I'm seriously debating returning my Captivate over this whole fiasco. The OTA hotfix that's pushing out today does nothing to fix this issue and I some how doubt this will be resolved any time soon.
Click to expand...
Click to collapse
According to Engadget, the latest update being pushed by AT&T "fixes" the gps issues: http://www.engadget.com/2010/09/22/samsung-captivate-gets-gps-fix-other-galaxy-s-versions-wait-pat/

compuguy1088 said:
According to Engadget, the latest update being pushed by AT&T "fixes" the gps issues: http://www.engadget.com/2010/09/22/samsung-captivate-gets-gps-fix-other-galaxy-s-versions-wait-pat/
Click to expand...
Click to collapse
Engadget is full of it.

foxbat121 said:
Engadget is full of it.
Click to expand...
Click to collapse
I think it is more that samsung "is full of it", because they are stating the gps is fixed. Engadget is just relaying what Samsung is saying....

Wasn't the source released for the captivate kernel? I would love to see the GPS source code
Sent from my SAMSUNG-SGH-I897 using XDA App

CLShortFuse said:
Wasn't the source released for the captivate kernel? I would love to see the GPS source code
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
GPS and most all of the drivers are not part of the source release.

Can we recompile the driver, does anybody know?
This is the source code for Nokia's driver for the same chip.
http://www.mail-archive.com/[email protected]/msg03733.html
But I don't think they use NMEA

Ok I hear what you are saying, I never messed with the settings and claimed that it was fixed. I am under the impression that my gps is working and always was but with the new jh7 firmware (ota version) it definitely works better, I had the samsung-firmwares.com release and it made no difference but designgears rooted decided version of thee ota release made a difference. What settings need to be changed to disable all network assisted location to test if I'm actually getting a gps fix without agps?
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Dani897 said:
Ok I hear what you are saying, I never messed with the settings and claimed that it was fixed. I am under the impression that my gps is working and always was but with the new jh7 firmware (ota version) it definitely works better, I had the samsung-firmwares.com release and it made no difference but designgears rooted decided version of thee ota release made a difference. What settings need to be changed to disable all network assisted location to test if I'm actually getting a gps fix without agps?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
Network assist is not a problem. There is no need to disable it.
Just take a test drive using Google Navigation. Ignore the fact that it always seems to be dead on your position (because all navigation software snap you to the nearst road). Instead, pay close attention to:
1. Whether or not you see a blue circle surrounding your position. If you do see that, your GPS has failed at that time and the size of the circle is the estimated inaccuracy of the GPS. You need to be patient because blue circle comes and goes randomly.
2. Pay attetion to certain landmarks like bridges, overpasses and intersections. And compare that to your position on the map to see if you experience lags.
3. The navigation software snaps you to the wrong road nearby even though you didn't see the blue circle.
In my personally experience, all three showed up randomly. I have no problem getting a quick lock at all.

foxbat121 said:
Network assist is not a problem. There is no need to disable it.
Just take a test drive using Google Navigation. Ignore the fact that it always seems to be dead on your position (because all navigation software snap you to the nearst road). Instead, pay close attention to:
1. Whether or not you see a blue circle surrounding your position. If you do see that, your GPS has failed at that time and the size of the circle is the estimated inaccuracy of the GPS. You need to be patient because blue circle comes and goes randomly.
2. Pay attetion to certain landmarks like bridges, overpasses and intersections. And compare that to your position on the map to see if you experience lags.
3. The navigation software snaps you to the wrong road nearby even though you didn't see the blue circle.
In my personally experience, all three showed up randomly. I have no problem getting a quick lock at all.
Click to expand...
Click to collapse
This has been my experience too...and while Cog 2.1 has made it better, I still experience these same problems.

I changed the first post and hope to make this a community effort.

The problem seems to be position estimation. When you take a sharp turn, the GPS position will keep going "expecting" you to follow the same path. After a few seconds, the GPS position will slowly return back to your real position.
If we could just remove position estimation / interpolation, we might see improvement.
You can see what I am talking about in my post here:
http://forum.xda-developers.com/showpost.php?p=8295858&postcount=2

Thank you ShortFuse.
This is the most truly helpful GPS thread in a while. I hope we can get to the bottom of this soon.
Everyone needs to contribute to this thread!

Verizon official 8107!

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...

My Unlocked Bell DZ Just Got System OTA Update

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.