Save and later upload client data for areas with limited cell and/or Wi-Fi only users.
The amount of data saved currently is insufficient to allow mapping of vast rural areas. Saving this data when storage is available and later uploading will speed the completion of your goals.
This is already working, though not properly and all devices. We are working on improving waze behavior in areas where the connectivity is not good, however, you will still have to start a new waze session with a connection .
It's ridiculous because the amount of data we're talking about is very small. There's no reason this data couldn't be cached on any phone while waiting for a signal again, no matter how long it takes to get a signal again.
Elanor Riley commented
As a map editor, it's extremely frustrating to drive to an area that needs work, only to get back home and realize you received no credit for going out there because the cell signal sucks. We NEED to be able to edit this data, regardless of if we have network signal out there or not. Cache our GPS data or something.
Very frustrating when you drive 6 hours through Norway to find out none of the reports went through nor can i edit the route. The phone was offline (roaming) with the preloaded route from when I left the hotel.
I imagined the data would be uploaded when entering Sweden and acquiring my mobile network back but nop.
Unfortunately this is not a problem only in "extensive rural areas" ...
It happens in urban areas very often.
in a route of 245 km, I get no internet hyper link for 30 ~ 40 kilometers and then it reconnects not more.
even it is 180 km with good quality 4G signal.
Only resolves to close the app and reopen it
The most amazing is the DEVs ignore our requests for help.
How long these claims are already here?
Since it can not solve the problem, at least give us a button "reconnect now" could solve the problem without closing the app and lose all trip data
We can organize a march of users if it who are waiting to give us attention
I have Waze on a WiFi enabled tablet. I have been able to use it when driving away from my house - and therefore losing the WiFi connection. So long as I go the way that Waze recommends, it works. However, if I choose not to use the suggested junction to the motorway - deviating from the Waze route - Waze then tries to find out where I am using the internet. That is a bit tough unless I drive back through my front room. Typically, I know the way to the local motorway network - it it the far end of the journey where I need navigation. Waze needs to be able to determine where I am on the route, even if I have deviated - whether that is by choice or by circumstances.
I notice that this has been an active suggestion for 5½ years, and 5 years since staff replied to it (and ignored it ever-since.) In that time, there are hundreds (if not thousands by now) of apps that are able to lose data connectivity, continue to function and store data and run with what it has locally, and then resume data send/receive when connectivity (either mobile or wi-fi) is restored without missing a beat of functionality. There is no need to end a session and create a new one once data is restored (making the user pay attention to connectivity state - which is dangerous for a driving app) and lose data from the previous session and/or start everything from scratch. Continuing to hide behind such an excuse - especially with the resources of google at their backs - is only a sign of poor programming skills and/or a lack of pride in product.
Mishoo MeHigh commented
I used waze on 3 different android devices and IT'S NOT WORKING!!!
I travel a lot with my job and there are some areas on a road that I've passed several times that never appear in the editor even if waze didn't shut down and even if I submitted the log files as soon as I had a data connection again
Hola sería muy bueno que las vías 4x4 se vieran en el mapa final del app diferentes a los senderos que se noten un poco mas.
Tobim91, it isn't working in any version, for any device, period. Never has been. And I don't know why they're so stubborn about spending development time on it to finally get it working properly. I've got a device with 128 GB of storage. There is no reason to ever give up trying to connect. And there is no reason to ever lose any data, because it can be saved locally until the network returns. And it ALWAYS returns. Waze just gives up and doesn't reconnect. It is ridiculous. And I'm quite sure is never going to be fixed.
I had some Connection Problems and these places are grayed out in WME. I think it is not working in Waze 3.9.6 for Android.
Nope. Latest version still craps out after half an hour or so of no connection. It's ridiculous.
Is this function added to latest waze? Since it mentioned started on 2010.
Me gustaría que las vías férreas se notaran en el mapa en vivo.
when you have no cell phone signal the waze have to allow the User to inform the traffic occurrences, should store data temporarily in smatphone and soon after you have the connection transmit the central database of waze.
Yup, offline behaviour is pretty sad. Even if you're starting in an area with signal, go through an area without signal, and go back into another area with signal again it doesn't always connect again. Waze should be checking for a connection every 5 minutes. Instead, it gives up after maybe half an hour and never attempts to connect again. What's more sad is the official response has always been "It checks periodically and will reconnect once it detects a signal again." But it doesn't do that. Not after half an hour or so. You can leave it running for hours after regaining signal and it still won't reconnect. So dumb.
Aaron Watt commented
I was going to say this but you lot already have, good to see I am not the only one with this problem.
Like everyone here I too don't like the fact that when in rural areas with no cell phone coverage and I come across roads either it be sealed or unsealed roads that are not on Waze Maps that I can't use "Pave" to record gps data. It's annoying that I can't upload these roads to the waze community because theres no cell phone coverage. Whats worse is that I can't "Add Place's" when in rural areas too. Waze App should cache the data when theres no cell phone coverage, then upload data when there is sufficient cell phone signal.
Karl Andina commented
I live and work in the high desert area of the Mojave in Southern California. I travel extensively through areas that do not have cell phone connectivity. As luck would have it, I will routinely pass a road hazard, stranded vehicle, or a police officer that I can not post for the safety and benefit of other drivers around me. I would love for Waze to have the capability to post something offline and once reconnected with a good cell phone connection, it uploads. I have noticed that there is the option to post later or to send now while in a good connection zone...why not add a similar function while not connected?
The problem there is Waze doesn't immediately reconnect. After a relatively short amount of time it won't reconnect at all, which I still can't believe has not been fixed. It retries periodically for maybe a bit over half an hour, and not long after that it just gives up. Or if it isn't explicitly giving up then there is a bug that prevents it from reconnecting. Quite annoying to lose that much data.
At a much more basic level, Waze users construct the best map of actual cell phone network coverage than anything the cell phone service providers have. So, it was seem reasonable to map coverage based on where the app loses connection and when it returns. This could be used to preload for the "dark" areas, just warn the driver that they are about to lose connection (useful when determining if a voice call is going to drop), and it might be nice in the case of route planning to pick the route with the best network connectivity.
Greg Sully commented
Hi, I appreciate there are / were similar suggestions to this, but Waze already has the architecture in the user interface to include the extra information.
I am not really a coder, but I can work out how to archive this in an interface through a paper designed structure.
At present, when you are out of range of a connection to the Waze servers via a mobile connection or wifi. When you click the report button in the user interface screen (bottom of screen in the right hand corner on my devices). The button in the form of an object, follows a set of rules to log that you clicked the button to report n issue where I presume, the time and location where the button was pushed was logged, so when at a later occasion a similar event logged by annother Waze'er, is backed up by the event you tagged but were unable to log further details due to a network connection failure.
So when it ones to implementing this change, at a very basic level (it's probably not as simple as I am suggesting), in addition to simply logging the time and location, gps if available and other navigation details. A aditional excicutionable action can be included, where aditional information can be included in the data update.
My fear however is a concern over the quantity of data that is being shared may be a underlying issue rather than the simply re-working the current system.