[SUPPORT] Android & iPhone app snap-to bug.

[troyv]

I become so interested in this that I started compiling a list of holes in a Google Spreadsheet. I may have taken some liberty on what qualifies as a "hole" for some of then, but others are blatantly obvious that there is something going on.

Interestingly, I found a lot along the Hampden and a lot along 6th Ave (where in spots it looks like noone even uses the 6th Ave Freeway). But then I had a hard time finding anything in between.

Here is the link:
https://docs.google.com/spreadsheet/ccc?key=0AhNq5f-y7qm3dHp0QV9pdzRHTmpZTFNwcnV2Vm4wV2c

[crazycomputingdotnet]

I know those areas are relatively flat compared to other areas around Denver (born and lived there for ~20 years) however I wonder if Waze 3 is only using 3 satellites and discarding the other 3-4 it can pick up, and those holes are related to one of the satellites being behind a building or mountain or in a valley, or it just losing signal to that satellite then picking up another satellite vs 2.4 using all satellite data. Maybe using more satellite means more memory / processor consumption and that was one of their ways of trying to fix the slowness/battery consumption of the new app. I think they are doing something similar with the frequency of polling for network connection and that is why there is a constant complaint in the beta forums of dropping GPS and network.

I wish there was a debug mode we could use where we could see things like cords, # of satellites, what Waze sees as network data etc to help them debug the app in the real world and not in an office somewhere.

[RallyChris]

As far as I can tell... at least on the iPhone, you cannot control the gps, other than if you are using it or not.

It is more likely that there is interference in this area that is over powering the very low power signals that GPS is.