What scale do we have? A 9 page thread on Macrumors with many of the same people posting in it? It could be less than 1% of beta users have an issue with GPS for all we know.I'm not sure what your point is. My point was that if the keyboard or screen thing were affecting very large numbers of the developer beta population, I don't think Apple would ship to "public" beta testers. I suppose I could have made that more clear. I'm not talking about the scattered problems here or there, but rather on the scale we've seen with this issue.
Extremetech said:The USB connection not only carries power and audio/video signals, it also carries the car’s GPS location information to the phone, a signal that may be more precise than the phone’s GPS. It knows and reports the state of the car: moving, stopped, parked.
installing (update) via IPSW fixed the GPS issue for me. Worked perfectly this morning.
What scale do we have? A 9 page thread on Macrumors with many of the same people posting in it? It could be less than 1% of beta users have an issue with GPS for all we know.
I agree. Some of the people on this forum are very vocal about certain issues and they almost made me skip the public beta because I thought that it was a bigger issue than it is. I installed it the first day it came out and I haven't had any GPS issues on my X. Other than a few minor issues here and there that are expected, I am completely happy with the public beta.
I think we can say at this point with a fairly high degree of confidence that all GSM phones are affected. However, the actual impact of that might be lower than it sounds at first. Wifi and cellular do a decent(ish) jobin built up areas and, as I discovered, CarPlay also allows the use of the car's GPS.
However if you fall into that special place on the Venn diagram where you rely on a phone for precise location and a) it is GSM, b) you don't have CarPlay and/or are navigating somewhere other than the car, c) installed a beta on a primary device you rely on for a) and require in circumstance b) then you probably don't have much grounds for complaint.
I'm on wifi and cellular right now, as confirmed by the GPS diagnostics app. There is no blue circle around me in Maps and I am, visually, placed fairly accurately in the building I'm in. GPS Diagnostics is quoting a +/- 214 feet accuracy. In short, you're wrong.You can tell this from the size of circle around your "gps dot" in maps. When you're on wifi/cellular the radius of the circle is massive because the accuracy is not great when it's not using GPS.
I'm on wifi and cellular right now, as confirmed by the GPS diagnostics app. There is no blue circle around me in Maps and I am, visually, placed fairly accurately in the building I'm in. GPS Diagnostics is quoting a +/- 214 feet accuracy. In short, you're wrong.
Edit: actually, for the sake of correctness, I have a very small blue ring.
Good for you. I think if you read through this, its not a few people. Have no idea what percentage of users this is affecting, though you don't get to 212 posts with only a few people complaining.I agree. Some of the people on this forum are very vocal about certain issues and they almost made me skip the public beta because I thought that it was a bigger issue than it is. I installed it the first day it came out and I haven't had any GPS issues on my X. Other than a few minor issues here and there that are expected, I am completely happy with the public beta.
I did not know that the vehicle GPS factored in. Makes sense, though. I'll have to check my plugged in/not plugged in satellite status.Thanks to the person who suggested the GPS Diagnostic app earlier, I now see why I get perfect results when navigating, even though I have a GSM 7+. It seems that when I plug in the phone to the car for Carplay I get GPS. Unplugged it uses cellular/wifi/Bluetooth.
Plugged
View attachment 768107
Unplugged
View attachment 768106
edit: Seems it's known and expected that CarPlay uses the vehicles GPS unit if available
https://www.extremetech.com/extreme...ay-and-wont-love-it-and-likewise-android-auto
+/- 158 feet is still pretty terrible isn't it? Isn't accuracy normally like 10-20 ft?If you're in an area where you can get 200 ft accuracy then the radius would be only 100 feet around you so yes you'll see a smaller circle. I bought that app just to show you I’m on GPS and apparently I have a GPS issue because I have a GSM phone.
If you're in an area where you can get 200 ft accuracy then the radius would be only 100 feet around you so yes you'll see a smaller circle. I bought that app just to show you I’m on GPS and apparently I have a GPS issue because I have a GSM phone.
[doublepost=1530214771][/doublepost]When you're on wifi/cellular the radius of the circle is massive because the accuracy is not great when it's not using GPS
Good for you. I think if you read through this, its not a few people. Have no idea what percentage of users this is affecting, though you don't get to 212 posts with only a few people complaining.
[doublepost=1530214230][/doublepost]
I did not know that the vehicle GPS factored in. Makes sense, though. I'll have to check my plugged in/not plugged in satellite status.
So I suggested that you guys reinstall the IPSW (update from B2 to B2 using IPSW) and after about a day, my GPS went badly again. However, I turned off location, bluetooth, and wifi and did it again and after 36 hours I'm still fine (I also haven't been using WiFi as much though). So if it doesn't work the first time, try again
DB2 is the same as PB1, here http://www.ipodhacks142.com/downloa...w-direct-download-links-over-the-air-profile/I’d like to try this method but I don’t think there is an IPSW for the public version, which is the only one I have access to![]()
DB2 is the same as PB1, here http://www.ipodhacks142.com/downloa...w-direct-download-links-over-the-air-profile/
+/- 158 feet is still pretty terrible isn't it? Isn't accuracy normally like 10-20 ft?
Anyway some folks are having gaps issues. I’m sure Apple is aware and will fix it.
No need to argue about who’s accuracy is better or circle is bigger![]()