Perlin, what about adding the version number into the Store's News section?
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
I assume most straightforward in "Waze-Web Pages (yml,html) / 3.7 Version - Store Text":perlin wrote:Not sure I know how to do that I'll try to find out.foxitrot wrote:Perlin, what about adding the version number into the Store's News section?
"- Bug & Crash fixes from May 30 release" - this string appeared just with 3.7.1
"- Stability & Bug fixes from Jun 6 release" - this one appeared just with 3.7.2
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Yesterday I've got a route without the ETA box being displayed (reported already for previous versions). This state persisted over multiple route recalculations. App restart fixed it.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Yesterday and today I've noticed a nice "grouped report", yesterday consisting of 3 single reports (a manual traffic report and two roadwork hazard pins a bit further) and today (it disappeared too fast to play with around). The triple report could be scrolled horizontally:
http://www.waze.com/forum/download/file.php?id=12240
Although the traffic jam report was just coincidentally in front of the roadworks along the route, I suppose that Waze logically tried to match them. Just that the color-coded traffic's line (where the first pin was placed at) always ends (with the stuck traffic as well) at traffic lights some half kilometer prior to the roadworks pins but never mind.
Two problems were bound with both yesterday's and today's multireports: they popped up as I was already a quarter hour past the location, and the map did not pan itself somewhere to them, but stayed at my current location.
http://www.waze.com/forum/download/file.php?id=12240
Although the traffic jam report was just coincidentally in front of the roadworks along the route, I suppose that Waze logically tried to match them. Just that the color-coded traffic's line (where the first pin was placed at) always ends (with the stuck traffic as well) at traffic lights some half kilometer prior to the roadworks pins but never mind.
Two problems were bound with both yesterday's and today's multireports: they popped up as I was already a quarter hour past the location, and the map did not pan itself somewhere to them, but stayed at my current location.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Today I've noticed multiple times, when my phone with Waze on background was sluggish, that it consumes a lot of CPU (in the task list, always red using up to 48% on a dual-core SG Ace2). Usually it is listed using some 2-3% or similar amount. Nothing helps, just client restart. Unfortunately unable to reproduce.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
For months long, occasionally an opened user popup can not be closed. It can at most be replaced with other user's popup. Only an app restart cures it. I'm seeing this a few times with each app version.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Funny thought I personally doubt they would implement such groundbreaking behavioral change and even that fast. Besides this, I still do see Waze among the consumers, in the 4% area, Maps is even lower. (I just can not manage to limit the hungry Android OS + Display tandem to consume less than their ~80% portion )a4bolek wrote:Funny, how ever since the "merge" Waze does not show as battery consumer. It is considered part of the "Maps".
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Not much, just an indeed damm unusually illogical dialog pageFlashBuddy wrote:Ya, I've been having a helluva time logging in on my Galaxy 2. While I can enter the username and password, there is no submit button, or login, or go, or any button at al. What is up with that?
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Sometimes it also happens, that particular drives do get processed with a few days' delay, especially during some outages (best to look into the editor, which are already listed there). It can then happen, that these drives will be counted towards the next week.usa_fpdk1bex wrote: My trip to DC started on Monday and I came back on Thursday.AndyPoms wrote:Also remember, the week runs Monday -> Sunday it is not a running total over 7 days.
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Hi,
Just moved over to Android from iOS - and Waze was one of the first apps that I installed.
However, I noticed that there seems to be no way of sending the voice prompts/directions to a Bluetooth device (ie, headset).
Under iOS it was there under Settings->Sound (Prefer Bluetooth), but that option is completely missing on my version of Waze (3.7.2) on my Nexus 4 (4.2.2).
Just moved over to Android from iOS - and Waze was one of the first apps that I installed.
However, I noticed that there seems to be no way of sending the voice prompts/directions to a Bluetooth device (ie, headset).
Under iOS it was there under Settings->Sound (Prefer Bluetooth), but that option is completely missing on my version of Waze (3.7.2) on my Nexus 4 (4.2.2).
Re: Android v3.7.2 Official Feedback Thread