Android 3.0.0.0 - official feedback post

These forums are specific to the Waze mobile app. Post here if you experienced a problem while using the app, have a question about the app functionality or a feature such as navigation or search.

Moderators: Unholy, bextein

Re: Android 3.0.0.0 - official feedback post

Postby guri211 » Thu Feb 23, 2012 11:06 pm

perlin wrote:A little clarification on the logic of traffic jam measurements:
When a user reports a jam, two things happen:
1. The speed measurement of this user on that segment has a double weight, and hence will affect more the real-time traffic on that segment.
2. His measurement along all the segment will be taken into affect (not just a short section/the specific spot he's on)

* The same logic applies when the user is prompted by the client "are you in traffic" and answers yes.

Hi Perlin, how is the "weight" handled please? Is there some minimal traffic jam weight required to change the ETA / reroute you?
guri211
Waze Global Champs
Waze Global Champs
 
Posts: 1725
Joined: Fri Dec 31, 2010 6:13 pm
Location: Bratislava, Slovakia
Has thanked: 791 times
Been thanked: 472 times

Re: Android 3.0.0.0 - official feedback post

Postby gerben » Thu Feb 23, 2012 2:32 pm

Version 3.0.1.0 is the current market version. Please upgrade!

Feedback topic for the new version can be found here
gerben
 
Posts: 4783
Joined: Sun Dec 13, 2009 10:42 pm
Location: Almelo
Has thanked: 33 times
Been thanked: 196 times

Re: Android 3.0.0.0 - official feedback post

Postby Kaimane » Tue Feb 21, 2012 11:32 am

perlin wrote:I believe this is a ROM issue but not sure.
What device are you using and what ROM do you have installed?


Hi perlin!

It really could be a ROM issue.
I'm using a custom ROM (Android 4) for my Desire HD.
Today I did an upgrade to the latest version of the ROM and installed the latest waze beta.
After upgrading and installing last waze everything works very fine for me!

Thanks for your help!
Kaimane
 
Posts: 11
Joined: Mon Oct 24, 2011 10:59 pm
Has thanked: 1 time
Been thanked: 0 time

Re: Android 3.0.0.0 - official feedback post

Postby AlanOfTheBerg » Mon Feb 20, 2012 6:12 pm

leo_lau wrote:
AlanOfTheBerg wrote:
Autourdupc wrote:Version 3.0.0.991 is out !
https://www.waze.com/forum/viewtopic.php?f=3&t=16353

4 days ago now. Yep. :)

Now New Android beta version- 3.0.0.992 is out ;)
http://world.waze.com/forum/viewtopic.php?f=18&t=16514

:lol:
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23614
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4822 times

Re: Android 3.0.0.0 - official feedback post

Postby troyv » Mon Feb 20, 2012 6:09 pm

AlanOfTheBerg wrote:
troyv wrote:What happened to the popup that shows you that there is a "road event" ahead?

Are you certain these are for hazards on the same road you are on and set by the other person for the same direction you are traveling?


Almost positive. I haven't seen one in weeks of traveling.

Because I am not 100% positive, and no one else is seeing it, I'm not going to push it. What I will try to do though is become more proactive and try to go after a hazard. If that doesn't work, in the words of Arnold Schwarzenegger, 'I'll be back'! :)
troyv
State Manager
State Manager
 
Posts: 125
Joined: Fri Jan 13, 2012 9:56 pm
Location: Denver, CO
Has thanked: 11 times
Been thanked: 19 times

Re: Android 3.0.0.0 - official feedback post

Postby leocylau » Mon Feb 20, 2012 6:08 pm

AlanOfTheBerg wrote:
Autourdupc wrote:Version 3.0.0.991 is out !
https://www.waze.com/forum/viewtopic.php?f=3&t=16353

4 days ago now. Yep. :)

Now New Android beta version- 3.0.0.992 is out ;)
viewtopic.php?f=18&t=16514
leocylau
Waze Global Champs
Waze Global Champs
 
Posts: 3714
Joined: Tue Jul 27, 2010 4:21 pm
Location: Newcastle upon Tyne, United Kingdom
Has thanked: 732 times
Been thanked: 494 times

Re: Android 3.0.0.0 - official feedback post

Postby cshubhra » Mon Feb 20, 2012 11:15 am

Did not see a response ... not sure if this was noted down or not ... a small update to it ... if I select an Arrow Head for my car, and de-select speedometer layer, the pixel problem is less ... but NOT eliminated.


cshubhra wrote:After running for some time (Some times, during loading), the street names, the speedometer, the car icon becomes garbled into a pattern of random RGB dots. I am using Android 2.2 on Samsung Galaxy 551 - I have cleared all cached data, but it did not help.
Also, It has become a battery hog - Probably it does not shut down cleanly. I deduced the shut down problem, because if I clean my RAM memory after shutting down Waze, my battery runs much longer than if I just shut down Waze and not clear my RAM
cshubhra
 
Posts: 20
Joined: Sat Feb 19, 2011 6:39 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Android 3.0.0.0 - official feedback post

Postby AlanOfTheBerg » Mon Feb 20, 2012 7:18 am

Autourdupc wrote:Version 3.0.0.991 is out !
https://www.waze.com/forum/viewtopic.php?f=3&t=16353

4 days ago now. Yep. :)
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23614
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1128 times
Been thanked: 4822 times

Re: Android 3.0.0.0 - official feedback post

Postby autourdupc » Mon Feb 20, 2012 6:58 am

Version 3.0.0.991 is out !
viewtopic.php?f=3&t=16353
autourdupc
Localizers
Localizers
 
Posts: 728
Joined: Thu Dec 29, 2011 2:25 pm
Location: France - Lyon
Has thanked: 0 time
Been thanked: 3 times

Re: Android 3.0.0.0 - official feedback post

Postby thefatveganchef » Mon Feb 20, 2012 2:21 am

harling wrote: I'm starting to wonder if there are any handsets running circa-2.2 firmware that aren't having performance issues of one form or another. (Samsung Transform, Android 2.2.2, gets a route immediately when stationary; when moving, after about five minutes of the map display lagging farther and farther behind, it finally times out with "unable to contact routing server", and then the map gradually catches up again.)

I've been trying not to be obnoxious about reporting this problem; as a software developer I realize how difficult it can be to track something like this down.

If a major version release turns out to be unusable on many older devices due to firmware/memory/CPU limitations, the developer should be interested at least in identifying the cutoff point, so that it can tell people with those handsets to stick with the previous release, rather than have an entire segment of people be disappointed at the (non)performance of the "latest & greatest" and give up on it altogether. Better still, is it that hard to profile the product while it runs on (say) a Samsung Transform with Android 2.2.2, pinpoint the bottleneck, and see if there is a feasible workaround?


I have a HTC Doubleshot which has a dual-core 1.2GHz CPU, 768MB of RAM, and Adreno 220 GPU, and a custom rom with a lot of the bloat stripped out and I have the same slow down issues in navigation mode. Sometimes it will be half a mile behind, and this is without it recalculating. It also is a battery hog. I can't drive more than 2 hours before I have to change the battery, and this is with it plugged in to a 2 amp battery charger. Waze 3.x seems to be very memory/CPU intense.
thefatveganchef
 
Posts: 1086
Joined: Sat Apr 30, 2016 3:36 pm
Has thanked: 0 time
Been thanked: 1 time

PreviousNext

Return to Waze App

Who is online

Users browsing this forum: handiestman