Im reporting some issues from the previous beta here, mainly because I cant put them on the old thread.

- Firstly I sent some logs last night when I had finished paving but not in a receiption area (so had not clicked the stop button) but Waze had the message 'Searching network'. To be fair it did fine the network for about 2 minutes but I knew it wouldnt last so didnt finish up. However when the network 'should' have come back (eg. I had full reception at home but still the 'Searching network' message) - I sent logs before turning off paving and then afterward.

These two are reports from the other end of share my ride, as I was driving I cant confirm exact details:- The share my route function works until there is no reception then it just stops and never catches up. eg. I drove from New Plymouth to Palmerston north (around 3 hours) however reception is lost just before Wanguanui (just over 1 hour into the trip), the people watching the trip were then told I was 2 hours away even when they checked just before I pulled into the driveway.

- On the share my ride page the other end sees 'apparently' the screen doesnt move with the car, so if Im going 100km I disappear off the screen and they cannot keep up. I would suspect this maybe because they moved the map slightly, and then didnt know how to get back to a follow mode?

Compared to the first Beta I tried this one was a marked improvement, I did have some other bugs but im hoping that the new one that was released last night will be just as good and I can test them again before the next release.

Another current state bug, the TTS for 'in X meters get ready to ...' should really be 'get ready to ... in X meters', from a new user perspective the current wording seems like the instructions will be repeated in X meters when in fact the action that happens then.

I had a weird display issue today but I dont have a screenshot (that whole using a cell phone while driving issue), the instruction was to in X meters keep left onto X road. The wording showed the X, but the on screen purple highlight showed the next road instead. ( https://world.waze.com/livemap/?zoom=9& ... ers=BTTTTT driving along courtney, instructions showed northgate, but line went to watson)

I dont mind the blue background of the night theme, but I cant see the smaller roads.

It seems to take a LOT longer to find a GPS signal, about 2-3 minutes. I use Lama to turn on GPS when Waze starts, however the store version only took 10 seconds to 30 seconds

There doesnt seem to be a way to cancel the 'Are you heading to ...' directions, if I click the X it routes anyway, if I leave it alone it defaults to Ok, and the only other button is 'Routes'. Could we have a 'No' button?

On that note, in portrait mode that popup takes up the whole screen, which is fine if im not driving but if I am theres no visibility of the map.

Its probably not a client issue but ill report it anyway, Great North Road (3) here: https://world.waze.com/livemap/?zoom=9& ... ers=BTTTTT (the main road) is a 50k area, however I noticed that it had a speed issue just before the turn off to London Street because traffic was going at 41-44 kph. This would be the first time ive seen a report for <10k, especially when all of the roads around it average under 50k.

In the morning Waze has started asking if im driving home, this maybe because the GPS has not kicked in yet and it has me a couple of blocks away fro home. But then when the GPS does kick in, ive arrived at home.

Waze is bringing up some really weird routes to destinations (Avoid Highways is turned off, and its set to avoid long dirt roads) when I say weird I mean 15 minutes longer than the normal route and avoiding ways to get to a shorter or faster route. I just tested one of the routes in the live map and it routed fine (two options provided one of 10 mins and one of 11 mins), however in the client neither option is given instead it wants to go out toward Egmont village (I havnt driven it yet as I dont have the extra 15 minutes) one of the routes is Essesx Street, New Plymouth to Alberta Road, New Plymouth (New Zealand) best route would be via Courtney Street however the client takes me out of town along Junction Road.

Autourdupc wrote:Very strange. I m 50000+ points and still do not have some sweets like first 10 miles !

Screenshot_2012-10-05-12-04-50.png

That screenshot shows you do have the one for the first 10 miles. Thats why its greyed out.

Although there seems to be some bugs with the goodies as we both dont have the same ones, (I can work out how to get two of them - although its nearly impossible as I am not a area manager).

First Fried on WazeHow do you add other people who use Waze as friends now? I convinced someone to use Waze this weekend but when I went to add them as a friend there doesnt seem to be an option, just map chat and message (both of which BTW seem to do the same thing)

Resolve 50 map problemsI assume if there are ever enough map problems reported that I can resolve I will get this. (BTW, something that would be nice against these is a progress of it, much like a lot of games to with achievements - in this case its on the dashboard page on the website but it would be nice if it was easy to see on this page/screen)

First report of a map problemIve reported many map problems, but have never got this one.

Top weeky user in your stateIn the state of 'NZ' (Ill forgive that New Zealand is a country not a state), Ive made bronze and silver so far, but never seem to get to gold (theres an area manager who always seems to jump ahead on the last day and ive given up trying for this)

Lastly, ive just noticed that 'Prefer goodie munching' has gone from the settings, I was going to suggest there should also be a 'Try new pacman routes' as well, that way I dont have to work it out when driving somewhere (option being to try and take a road that needs checking even if its slightly off the normal route).

0. GPS LOST WITH SPEED CAMERA POPUP! AGAIN! LOGS SENT: 6:40 AM GMT.1. Horrible black bar on top STILL block big portion of screen in landscape mode.2. Pressing menu while having route, STILL opens menu with scrollable buttons. Thats horrible Just open fullscreen menu, with ALL buttons on screen.3. Speedy Mood STILL looks like DUCK. Get back original speedy mood.

What's fixedNetwork related crashesCrash when received "Thanks"Crash when popped message "Are you in traffic?"Invisible mode - your session is not registered, no one can see you on the map or in destination screen or online in friends list (after the ticker that says 'Adding you to the map' appears, there's a period of 30 sec allowing you to become invisible before the session gets registered).Many other crash fixes

Known issues4Square check-in not working yetShare on FB from destination screen not working yetThe "Closure" feature doesn't work yetWhen pickup route includes stop-point - canceling stop-point cancels pickupMute button in main menu is not synced with mute button in the nearing destination barCan't un-park (cancel the parking sign)FB pics in user details exceeds frame (on Milestone, GS2 & Motorola Razor devices)Pickup session might end if waze is sent to background

Since a couple of weeks I changed my HTC DesireHD for a HTC One X. I found out fast that Waze closes more often in the background on my new device than on my old, although its specs are higher. That has been this way with the current market version and the last 3.4.99 betas. Switching from Waze to the gmail app and reading an e-mail can be enough to trigger this.

With closing in the background I mean that the Waze icon stays in the task bar, but when switching to it, Waze relaunches as if it wasn't running at all.

Apparently, the One X (or Android 4) memory management is more aggressive. I'm never using any task killers.

Here's some info on this subject, that was found during the development of Flitsnav, a Dutch GPS program that was experiencing exactly the same during development. I hope it can help you improve this behaviour, since several users are reporting this.

Waze closing in the background has to do with Android's Out Of Memory (OOM) management.

Some info on OOM_adj (-17 tot +15): The LOWER the value, the MORE important Android thinks the process is.

slow_mo wrote:I saw someone mentioning this problem, but since it is still not fixed in this beta but was present in two previous betas, I'll report a bug here.

The problem is that a speedometer disappears when adding a stop and pointing to a location on the map.

Steps to reproduce:

Navigate to any place

Go to menu and select "Add a Stop"

Go back twice to get back to the main screen

Tap and hold somewhere on the map and then select the blue arrow to the right of the popup

Press "Go" in the next screen

Speedometer will be gone.

Let me say that current way of selecting a point on map as a stop is not very intuitive. Better way would be to have a separate button saying something like "Point on Map" in the Navigate screen besides Categories, Favorites and History.

Actually, it's more complicated than that. The way you've described to add a stop is not legit. It is a bug that a stop has been added to your route... If you're tapping the "Add a Stop" button and go back twice, it should dismiss the selection. You're not supposed to be able to add the stop from the map. So in fact you found 2 bugs. Thanks

porubcan wrote:installed over .109 without problems, all settings preserved.

many small bugs/issues reported for .109 and .106 are still present:* mismatched moods: bronze and gold are same, speedy and duck are same), * navi bar in landscape is too big, * popups have different controls (wazer's don't have close X button and is not being closed by pressing back button), * wazer's popup goes off the screen, * settings->social networks->group->Pop-up reports and Group badges - cannot be modified (if you modify and exit settings they are reverted back to "none" and "From all groups I follow".* menu scrolling is not very comfortable, moreover there is enough space to make menu box larger to get rid of scrolling.* textboxes for reporting jam, police, accident, hazard and map chat have first line of text misplaced (too high)