2 replies to this topic

[ForestCat]

This is a longshot, but is there anyone who still uses an XT926/XT925 who can verify whether or not the GPS function (as opposed to Google/VZW/WiFi location services, etc) is still usable, and if so, what ROM?

 

I have three different XT926's, and they've all become so inconsistent/unreliable since the GPS Week Rollover in November that they are unusable for navigation, hiking, etc.

 

It may be a problem endemic to Snapdragon SoC of this vintage, and I doubt there will ever be a patch for the drivers.

 

It's always been a great device for offline nav (hiking. biking, boating, etc) even without a SIM, because of the unbeatable (even in 2019) battery life.

 

Really hoping there's some solution.  I still love this phone.

[livinginkaos]

Wow, long shot is right - but you never know.  I don't have one of those left in my "old devices" drawer, otherwise I'd check it out - however, I do know that it is a firmware issue within the GPS and while iOS can fix it with an update (for devices that can still update to or beyond 10.x.x), android users are not as likely to be able to manipulate it within ROM parameters as the firmware is proprietary to the chip, not the OS.  Part of the whole issue that's plagued android from the beginning - fragmentation.  You can keep an eye on things over at XDA, but I wouldn't be too hopeful.  I will reach out to a couple of old dev's from yesteryear and see what they say.

[ForestCat]

Thanks, man, I appreciate it.  Yeah, I'm thinking it's a function of the embedded microcode for the gps within the Qualcom SoC.  But I don't know.  It's still acquiring satellites w/ decent strength, and I THINK you can still see NMEA data at the OS level, it just randomly refuses to get a LAT/LON fix. The other days it works like a charm.  Sky cover is not the issue.

Makes me wonder if there's a way to patch the HAL to fix this, or if the determination of LAT/LONG occurs at the silicon level.