Shorty-CM
My feedback
1 result found
-
1,562 votes
AdminElla (Waze Team) (Admin, Waze) responded
An error occurred while saving the comment An error occurred while saving the comment Shorty-CM
commented
They should really allocate what can't be a very large amount of time to get this working properly. It should be able to cache data until the phone runs out of storage space and should be able to then upload everything that is cached when either signal returns or you return to wifi.
An error occurred while saving the comment Shorty-CM
commented
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.
An error occurred while saving the comment Shorty-CM
commented
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.
An error occurred while saving the comment Shorty-CM
commented
Nope. Latest version still craps out after half an hour or so of no connection. It's ridiculous.
An error occurred while saving the comment Shorty-CM
commented
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.
An error occurred while saving the comment Shorty-CM
commented
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.
An error occurred while saving the comment Shorty-CM
commented
Yoshi, I'm going to paste your comment into a bug report in the beta project. That's something that definitely would be better if you were able to do. I don't see why it couldn't just use your last position as the spot to flag.
An error occurred while saving the comment Shorty-CM
commented
Sometimes I wonder if it wouldn't be faster to go learn Objective C and submit patches ourselves, hehe.
An error occurred while saving the comment Shorty-CM
commented
Waze doesn't *instantly* learn. It won't show any improvement from people's drives until the scheduled tasks run on new data. That takes time.
An error occurred while saving the comment Shorty-CM
commented
I'd be surprised if any work was done on this at all.
An error occurred while saving the comment Shorty-CM
commented
As long as you don't lose your connection, yeah.
An error occurred while saving the comment Shorty-CM
commented
Zero.
An error occurred while saving the comment Shorty-CM
commented
Yeah, it makes no sense. They already have existing code to upload saved crash/debug logs. Go figure.
An error occurred while saving the comment Shorty-CM
commented
No change, I'm sure. Doubt they'll ever fix it, frankly.
An error occurred while saving the comment Shorty-CM
commented
Wish I knew. They might think the feature is currently working, but it doesn't seem to be working quite right. And it sure doesn't work as well as it could. Lately I have trouble even getting it to pave new roads at all, even with perfect connectivity.
An error occurred while saving the comment Shorty-CM
commented
Nope. :(
An error occurred while saving the comment Shorty-CM
commented
Why do you have to start a session with a connection? And is that going to be fixed? The activity described in my earlier comment should realistically be possible.
Shorty-CM
supported this idea
·
An error occurred while saving the comment Shorty-CM
commented
I should be able to fire up Waze in the middle of the desert with no cell towers or wifi for thousands of miles and record roads. Never having any type of connection for weeks on end. Recording thousands of sessions, and thousands of roads. And come back to civilization, fire up waze on the wifi, and watch as it uploads 3 GB of data.
Yes, I'm serious.
Happens all over the place in Canada, too. It's annoying and counterproductive. Should be insanely easy to implement, so why they don't just take a few minutes and do so is beyond me. But then, they've got weird dev ideas there now compared to years ago. Not actually listening to users is both aggravating and odd.