In the previous version, when I wanted to save a location if I was not in a road the application would simply crash and exit the program.
Does the new version has this small issue fixed? It would be cool to be able to save locations, on your first trip there… even when the road does not exist yet!
Regards,
I just drove a few kilometers with 1.5.2.1 with my Milestone (Android 2.0, no hacks, customs roms or anything). it feels faster, but this may only be due to the fact that I deleted the waze directory on the sd card (which worked sometimes for the old versions too). The previous crashes I experienced were not in the city but on my way to regions with not so good network connections all the time. I will try to test it again under these circumstances. I will also scroll over the map tonight, so that the software will preload as much tiles as possible from roads I have previously driven and edited. We’ll see how this new version deals with a lot of files.
One thing that was new, was the fact that several times the screen went blank, the only thing left was the Android status bar at the top. I don’t know if the software wanted to switch to landscape mode or whatever, I was just confusing, because every time you expected the software to crash. It recovered however after a few seconds.
On one street while wazing there was an error message and it reset the street. Unfortunately I didn’t make a note of the message. Will try again tomorrow if I can.
Switching streets from the little dotted lines to complete lines seems smoother, however I want to try again with new tiles and lots of edits.
I really hope this new version can keep it’s promises, so it’ll be fun again. I’ll install the new 1.5.2.2 now and preload the files and test how fast the software will react on what I do on the screen.
One last thing: The automatic dimming or switching to night mode worked in not a single version I have tried so far. Android bug or what?
I just had my two test runs with version 1.5.2.2. As I said yesterday I scrolled a lot around the map in 2D and 3D and performance so far seems good, also in settings menu. The icons (car or cookie) does not always seems to match what the program is doing, but I guess it’s to enhance performance.
The issue with the screen going blank (more often in the 1.5x version) can be fixed with manually turning off the automatic screen rotation. However it should be in the waze settings, so you don’t have to go always in the android settings to disable this feature.
Due to the not so detailed map data so far in Hamburg I never got the software to calculate a route, but today it worked for a short route. 4 km with 4 turns. It crashed after the first turn unfortunately. Log has been send by mail.
Yesterday the 13th I was on the 1.5.2.1 or 1.5.2.2 and there must be something wrong with points and the new beta.
I don’t remember the exact point score I had yesterday but I am pretty sure it should have increased to more than it is today.
I have all of the driven kms in my dashboard, but doesn’t seem to have gotten any points.
Yesterday I also did way more map editing than I normally do as well.
It can’t be true that you are supposed to drop 5 positions with over 300 KM and several hours of map editing.
Could you please look into this, and if its correct explain why I haven’t gotten any points, or so few.
Today I was on the 1.5.2.3, and hope that haven’t done anything funny as well.
Thanks a lot for new bug fixes! But I must ask you again to bring back old-style bottom menu as option. It’s very, very, very inconveniently to:
find and press small and dark hardware ‘Menu’ button;
wait until native menu appears (there may be very long delay at that step!);
try to hit proper menu button;
try to do something following by that (send road report or something else).
Note that all these steps I must pass while driving a car, instead of looking forward to the road! It’s not only inconvenience, but every exessive dialog and every exessive press to the menu button is really dangerous to driver! That’s why i stopped sendind road reports at all. Do think of usability!
By the way, is there any easy way to make waze client to return to my current position while on the way? Every accidental touch to the map screen makes waze client to stop following my motion and the only way to return to my current position is to pass all that nightmare with menus again and again. If you determined not to bring old-style menu back, maybe you should allow user to chose on-screen buttons to quick access frequently used functions?
that’s a good idea, i’d also like to see some on-screen buttons to which you could assign actions from the menu (shortcuts, anyone?). it would also be helpful to have a toggle in the menu for the screen rotation (portrait / landscape / auto - based on whether it’s enabled by the device or not)
Why we don’t have any classic color scheme? Like red, yellow, green, etc. roads? I don’t like any of themes supplied Maybe same colors like in web editor could be good enough…
yup, in most of those color schemes either some type of road blends in with the background, or two types of roads look the same … or both. maybe a color picker could get incorporated into the menu? (sorry, i know this isn’t the suggestions thread…)
Note we are going to put it in the market in a few hours.
Regarding the menu, we will see about enabling an option to set the old mode. This mode was done to be Android UI compatible but I understand the issue of additional clicks.
Regarding the colors, we will look into more schemes, problem is that the jam colors are already red,yellow,orange (and we didn’t put green as well) so we are running out of colors.
thanks for the updates, which come pretty fast. Great to see there is always improvement. What about the landscape mode switch? Is there any way the program can disable it in the near future?
There seems to be a limit of 4 MB on the SD card for the entire directory. Is there a way the program can cache more data, maybe some option in the preferences? What’s the map.cache option for, should it be increased to run smoother?
Tried to use Waze on my ride home from work today but the app was very laggy and it kept saying seems you gotten of route but i was traveling on the route. This was on my moto droid running the 2.0.1 software, not rooted, not moded… almost seemed like it needed way to much memory to work right. Please help so i can get back to wazing.
It didn’t crash until it had run for 10 hours and around 350 km.
Don’t know why it crashed since I didn’t look at it at the moment, but it was inside a very long tunnel.
Other than that it worked fine, no problems except for the Volume control settings, the day/night light and the automatic night mode.
For me this is a big improvement, all the other 1.5.2 beta versions have crashed around 5 times over this time/distance.
And the same goes for the market version before the first 1.5.2 beta.
In fact I am so impressed that I will stress test it during this weekend, maybe I can go back to using only one phone, and don’t have to bring my Nokia to make calls with.
Have been running for 24 hours straight while I have been at home, and using my phone for everything else as I do normally. Seems to be a very good and stable version