I’m frequently getting the “No Network” message, stating that live data will not be available, while using the Waze client. However, I’ve noticed that my 3G connectivity is working and I even receive e-mails and Google Talk notifications while this message is showing. Therefore it is not the network at all. Perhaps Waze’s servers are going offline ? Anyway, the worst incident of this was today, where for a 30 mile journey, Waze only came online for the last 2 miles. This was from 4pm to 4.45pm today.
Could someone please elaborate on what the problem is ? Is it a server problem ?
Using Waze v1.7.2.12 on HTC Hero with Android / HTC Sense v1.5, Build number 2.73.61.66. Worked ok until very recently, as I only noticed the problem today. :?
I think v1.7.2.12 is the latest version, isn’t it ? I’ve not had my Hero long. It’d be good if they sorted this out as it’s one of the best apps out there.
hi guys,
we weren’t able to reproduce this problem, but we suspect it is related to a new data compression mechanism we’re using. As pevans_om suggested, please try to upgrade to 1.7.2.15 (now available on the Android Market as well) - it should solve this problem.
Keep us posted if it helped / didn’t
I just downloaded Waze a couple of days ago. Used it for the first time today as I didn’t leave the house. I got a “No network” message twice when I went to leave my house. Not I was still connected to my wifi and it was working. Then when I went out of range of it, it took a couple of minutes before I got that message. I tried to close the program and load it back up the second time I left my house so I was on the cell data and not the wifi. It was working then I get down the road and I lose network again. I checked my data and I had no data what so ever. I had full bars for cell reception. I don’t know if this is a problem with my phone or just this program. When I left work and used it, it worked just fine. I also know that where I lost signal, usually there is a dead spot there for a brief moment. But when I get coverage back, it don’t reconnect. Was wondering if anyone else has had a problem similar to this. If you need more info, feel free to ask.
I think I know why this happens, atleast for android phones. I never got the “no network” message until several days ago when I changed a setting in my mobile network settings. On my phone (Droid Eris) the setting is “Enable always-on mobile data” which I disabled so the phone wouldn’t be draining battery by always searching for/using 3G. That way applications can connect when they need to but the phone wont always be searching/connecting. Anyway, after I disabled that I started getting the no network message, but also had no problem with loading maps… so maybe it’s a bug fix we can suggest for the next release…
Try to set your phone to GPRS or Edge when wazing. Over here the 3g coverage can be spotty, and Waze does not like the switches between 2g and 3g. When I disable 3G, Waze runs a lot smoother and crashes far less.
Apart from the 2g/3g-issue, I find that the message “Searching for network” is misleading, since the search itself takes place in intervals. “Last time I tried, 60 seconds ago, I found no network” would therefore be more accurate and explain the behaviour: a physical connection was built some time ago but Waze doesn’t benefit yet.
Part of the problem is when you try to post reports when there’s no network, instead of queueing them like it should, until network connectivity is restored, it throws up an error and ditches your report. Poor. This is something that they need to work on.
