Waze forum

The new Android alpha version 1.8.99.104 ( 1.9 pre-release ) can be downloaded from
http://tiny.cc/1899104

Updates and fixes:

* Large log outputs while navigating (which is probably the reason for the freezes and crashes)
* Navigation bar fixes
* Physical keyboard numbers and symbols input
* UI fixes in Data Usage dialogue
* Gracefull exit on shared library failure

Indeed - message received. I think I mentioned in some threads, but in case things require our response, please just add to the title something like "Request SUPPORT Response" so that we will be able to identify items which require our attention.

And to the issue at hand: we are very much aware of the Nexus/Froyo related issues. We've got crash dumps and logs and have been trying to figure this out for weeks, finally getting Google in the loop as well.

Seems that when the Froyo is overloaded, it starts to crash. My gut feeling is that this is the reason that Froyo has not been officially released to any platform other than the Nexus and that there are issues which are being dealt with regardless of waze.

We have seen similar crashes on unofficial roms of 2.2 installed on other devices (Samsung Galaxy as an example) and hence I hope (though I have no information about this) that the Android masters will issue some 2.2.x version to fix the issues.

We are and have been spending a lot of time investigating this and we are just as frustrated as you are about this (we get many emails regarding the issue) but so far did not manage to circumvent this issue. We see Android as a major platform and our focus is to get a release out, but these issues must be corrected. If by some chance we will get information to enable a correction, we won't hesitate to issue a patch release as well.

So I hope this clarifies the issue.

OK - I'll try to cover most points raised.
We have had crashes in previous waze version - but we did manage to collect crash dumps and correct the problems - here it is an elusive problem that is eluding us. Of course, at the end of the day we should do something in the application to prevent it but if there is some race condition in the OS level that is triggered by background running (and our other activities when in the background, like calculating route, collecting GPS points, transmitting data, etc...), it might not be entirely in our hands.
Only auto shutdown we implement today is for low battery (I.e. if battery is less than 20% and <Continue> is not selected, app closes down). The OS has its own mechanisms - for example in case there are several apps open and there is shortage of memory, the OS can shutdown the application (see below how it appears on our side from the Android market reporting tool).
http://img827.imageshack.us/img827/2536/memory1.gif
As I indicated, we are working directly with Google to see what we can do here, as obviously if 2.2 is installed on all devices, things are going to get uglier without a solution
Regardless, I do hope we have a beta version next week, but it is too still necessitates to be stabilized first.

We are still working on it - weekend as well, but unfortunately still not having a clean enough version to provide as a replacement for the 1.9 version. Most R&D efforts are concentrated on this Android version and this is the main task we are working on.
Once I have something, it will be posted here and in the beta post thread.

rcocchiararo wrote:Posible bug:

Using SWYPE keyboard, i cant delete when commenting on the reports.

I think its also not posible to change input method ir copy text from the comment box, so that might be the reason.

I'm using Waze 1.9.0.0 and I'm still having issues with Swype. I'm not able to delete characters or change the input method. Any progress on that?

Thanks,
Tiago

Just read this topic and seems I have the same thing going on

After my GPS on my Touch Pro 2 broke down a few days ago, I bought the Galaxy S today, installed Waze on it, but I noticed it has several problems.

For one, whenever you have to input text, whereever (like usernames, passwords and such also), you can not use backspace when you make a typo. It also remembers the data you put in, so you have no way of redoing it if you have saved it accidentally.

Now, whenever I start Waze, my phone freezes and after a while it either resets itself or I have to remove the battery if it doesn't reset. It is impossible to use Waze with this phone apparently... kind of sad because it is a killer phone imho.

Soooo no Waze for me for the time being.. the Galaxy S can't use Waze and my TP2 has no working GPS anymore (which actually happened after installing the WM2.0 Beta version, but I doubt that had anything to do with it.. I had GPS problems before, and that phone was dropped quite a few times by my baby girl (no worries, this new phone will be kept away from her by miles lol)).

rcocchiararo wrote:The backspace is a swype bug on NON standard text boxes (waze 2.0 will abandon the custom textbox, so that will "fix" it in the future). You can always use a diferent keyboard, or in waze options deactivate the phones keyboard (that will leave you with an UGLY waze kb, but backspace will work, just for waze, of course).

If your galaxy S already has android 2.2, you should wait before using waze, until 2.0 is released, if not, dunno, i was able to use waze more or less ok on 2.1

Yeah just read a nice fix in another topic on the swype thing, it's a bit easier (and nicer)

As for my android version, the build says 'eclair', so I'm guessing it's the 2.1.. but yah, can't use waze at all, it hangs as soon as it is started (usually when my own location was just found) so I'll just wait for Waze 2.0

Great update, I like the UI changes. The directions looks much better imo. I have not noticed any new problems. The only thing is that I still (and have not been able to for a long time) cannot report a problem as a missing road. When I select it and press send it does not do anything other than highlight green while holding it. Once I switch to any others such as general map problem, then it sends immediately. Thanks for the great work!

alex wrote:

Lemon wrote:Has anyone else been using 2.2 froyo with this version of Waze (1.8.99.104)?

Mine works so far but a lot of the writing is blurred in the application. Just wondering what other users experiences are so far?

StefanSarzio wrote:I've got that too.

What bothers me more is that Waze hangs and needs to be force-closed when you de-activate car mode from the notification bar.

Hi Lemon, StefanSarzio
Version 1.8.99.105 ( http://tiny.cc/1899105) is supposed to resolve this issue. We'll appreciate your feedback,

Thanks in advance,

AGA

I never noticed the text blurred. I did have it where it would show little boxes around each text element, but never had it blurr.

Lemon wrote:To anyone using a Nexus one with these beta versions, have you had the following problem:

My hypothesis is that while in Waze touch input near the bottom or in the bottom half of the screen is perceived as touch input at the very bottom of the screen.

When trying to report a problem on the bottom half of the Nexus One while in Waze, i am often presented with reporting a 'foursquare check-in' report, though i'm trying to report a 'chit chat'. It usually takes several tries to get to the 'chit-chat' report. Once i'm in to the chit chat, i want to enter a description, so i tap the description text box (near the top of the screen). No problem. I'm in the text box now, the keyboard pops up. Now i'm not using the android keyboard but Swype (you swipe to each letter in the word to create your text). Now i feel this way because in the Swype keyboard you can half your Swype path be recorded. When i start typing any key away from the bottom of the keyboard, that touch input is immediately recorded as a touch at the bottom of the screen. I assume this is what is happening when i am in the 'select reports' screen as well (why i get a foursquare check-in report when i want a chit chat).

This is hard to explain but is anyone else experiencing a similar issue on your Nexus One with Waze? This has not happened in any application besides waze since i've had this Nexus One (3 months).

I have had no problems similar to this. It sounds like it's a calibration issue, though you said you're only having this problem in waze, so that's a bit strange....