I have a bit of a problem with these 3.0 versions. I am tempted to go back because it is frustrating in a way. I don't remember how it behaved before, but I am tempted just to install the old version for comparison. But I guess someone could argue that it wouldn't be a fair comparison because of the different software models and code running from 3 and 2?
I never had so much problems with the network handling as I do with the 3.0 versions (including the betas in 2.99).
Listen, I don't know if it has been mentioned, it very well might have been, but I hope that they have noticed it and are working on trying to fixing it. I run the Nexus S 4G phone, and it isn't loaded with bloatware. In fact, it didn't make a difference if I was running Gingerbread or the ICS 4.0.4, they both act up under what I call, certain circumstances. And frankly, I think it needs fixed, and rather urgently because I see that as a major downfall, and producing navigation errors as it did with me.
I have tried this with Google Navigation today to compare, and I don't get the same effects, it tracks along with me just fine, in and out of network coverage area changes. But when I run Waze, it reports me as stopped and then throws the pop-ups of events nearby. It also will put me on certain side streets, and then when I look at the route history in Waze, it says that my GPS reported I was on that street, but come on...I am not some fool, I do more with my phone than just run an app, I am very analytical of how my phone operates, the limitations, the accuracy. This phone has a better GPS compared to a Vibrant I used to run, and even the version 2 of Waze on the Vibrant didn't give as much of problems.
So I am tempted to try to run version 2 as a comparison to show that I am not dreaming this up, that there is legitimately something going on, be it from over processing that it wants to overreact to sensor data, to handling network coverage changes better? And this doesn't matter if I have 4G on or just running 3G, but I would say it is potentially worse with 4G, but hey, I'm going to flip flop here on this because it seems like it equally does it on 3G. I can almost predict when it will happen on 3G, and it is going on the highway, from the tower in my town to the tower in the next town. I can plot it with network.sprint.com to show the towers and I am sure I am going to notice it more at freeway speeds than say at 35mph in town speeds, but I have seen it do the reporting of no GPS, not necessarily an error, but the 0mph indication even though it moves with me on the map, on 35-45 streets.
I don't know all the facts, but I personally feel, in my opinion, that Waze is not processing the data in a way that could be actually better and less error prone. I mean, what is Google Navigation doing differently in the data for the sensors and GPS that could be ported or implemented to Waze? I'll be a test bed but I figure if I don't say something, nothing will be done about it, so here is some feedback, not to be flaming the issue, but please fix it.
On another positive note, the better handling of the landscape errors in ICS, much better! Thank you thank you! The update came faster than me getting on here to say or mention it too. Thank you for the fast updating that is going on, for a period there last year, it seemed like dev was not going on at all, my hope has been restored! Thanks for all you do, and let me know if there is anything else I can submit to help in this targeting of the problems.