New Android Beta Version - 1.8.99.106

[gerben]

I wonder if the crashing problems are related to specific phones.

I sort of suspect that the older, less powerful phones are the ones having the force close and crashing troubles. That would explain why my friend's G1 crashes almost every time he tries to use it, while my Evo has rarely crashed at all.

My G1 caused to crash a lot (some app only crashes, but also total phone crashes). The last month, GPS reception became worse and worse. First I thought the GPS problems were cause by my new car but after I did a factory reset because of another problem, evering is running a lot smoother, even though I've reinstalled almost all my old apps. Crashes are now incidental in stead of 1-2 times a day.

[tskramp]

I wonder if the crashing problems are related to specific phones.

I sort of suspect that the older, less powerful phones are the ones having the force close and crashing troubles. That would explain why my friend's G1 crashes almost every time he tries to use it, while my Evo has rarely crashed at all.

Mine crashes on my Nexus One. Not that often, but usually after it reboots my phone, when I try and start waze up again when it comes back up, it then reboots 5 seconds after opening waze. so I generally just don't use waze again during that drive.

[unwallflower]

I wonder if the crashing problems are related to specific phones.

I sort of suspect that the older, less powerful phones are the ones having the force close and crashing troubles. That would explain why my friend's G1 crashes almost every time he tries to use it, while my Evo has rarely crashed at all.

[IvarKa]

Lot of crash reports here. Mine in just slooooow (HTC Hero 2.1). After clicking menu button or on the screen it takes 5-10 seconds before it responds. Phone and other apps are running ok.

Ivar

[vikos]

Hi,

for the guys who want to leave Waze: My suggestion is, to run it in background and use Google Nav instead. Thats the way I do it currently. Have not had a single crash running it in background, but a lot when I ran it in foreground.
You will at least gather data and can choose to take over a more active role once everything runs better...
I do not expect that Waze will be usable for the "big public" in Germany for the next one or two years, but at least I gather data and do updates in the editor from time to time. Navigation is still almost completely unusable here...

when waze reboot phone, its hard to run it on background so I am still try to found new users, but the are mostly on android and have troubles with app stability

Sent from my HTC Desire using Tapatalk

[myld]

Google Navigation is only available in some countries, so that's not an option in Sweden for example.

A few posts back I said that I had no crashing problems with Waze, but this morning it did spontaneously reboot my HTC Desire with Android 2.2 and Waze 1.9.0.0 while it was in navigation mode guiding me to work (I was verifying a couple of roundabouts I had corrected in cartouche).

[Ayindi]

Hi,

for the guys who want to leave Waze: My suggestion is, to run it in background and use Google Nav instead. Thats the way I do it currently. Have not had a single crash running it in background, but a lot when I ran it in foreground.
You will at least gather data and can choose to take over a more active role once everything runs better...
I do not expect that Waze will be usable for the "big public" in Germany for the next one or two years, but at least I gather data and do updates in the editor from time to time. Navigation is still almost completely unusable here...

[unwallflower]

It IS a shame that waze has been losing quite a few followers lately.

I feel like I'm the only android user who ISN'T encountering stability issues. Waze has maybe crashed on my phone twice, if that. However, I have a friend who stopped using waze because it was unusably unstable on his android phone. Wonder why we aren't experiencing the same problems? Both of us have 1.9 installed.

I'm mostly satisfied with waze, although I am disappointed in its unreliability in other areas. I'm still missing a route that support said was lost, then claimed was found... but it never showed up. *shrug* It is what it is. I no longer spend the same amount of time editing maps as I used to. It just doesn't seem worth my time when everything is so unreliable. I just hope it becomes more stable eventually.

[tskramp]

But Waze guys, please, ease off on the love for the sodding iPhone! You may argue that 'most' of your users are on iPhone, but even if, for example, 40% of your user base uses it (which I find hard to believe), that's still 60% - the majority - that don't. Issuing updates for the iPhone long before anything else, and really making a big deal of it, serves only to annoy the users of other platforms that don't have - and probably don't want - the overpriced, overhyped POS. Spotify (European music streaming service) have the same kind of philosophy, and really get flamed on their blog comments for it. It would be far better to have simultaneous releases for all platforms, and if that's not possible, at least have a beta available (even better, nightly builds as damaniac suggests), that we can try out and give useful feedback on.

Even if they're largest base is iPhone, I would imagine that the number of users on Android is catching up. There are several articles about how much/fast Android is growing, it's only a matter of time before the Android user base surpasses the iPhone user base...
http://androidcommunity.com/200k-android-phones-sold-every-day-20100805/
http://androidcommunity.com/npd-android-passes-blackberry-in-second-quarter-20100804/
http://techland.com/2010/07/08/androids-market-share-continues-to-climb-while-everyone-else-slips/

[grebble]

Yes it is a shame to see people quitting. It depends how much patience users have with the project. I for one love the concept, and that is the only reason why I'm sticking with it. We're indeed not paying for it, and it is still early days so issues will occur. However, that said, I have stopped using Waze on my phone until the new beta arrives, because of the stability issues. I won't go into how and why it crashes on my HTC Desire because I've said it before, and the devs say they are working on fixing the problem. It does, however, seem to be far worse when auto brightness is switched on, but one thing with Froyo is that it doesn't seem to freeze the phone any more, it just reboots it instead

Going by what has been said on the blog, the number of Waze users has absolutely skyrocketed recently, which is why the drives are taking so long to show up, and the guys need time to get the infrastructure sorted out to cope with it. I'm prepared to give them that time.

But Waze guys, please, ease off on the love for the sodding iPhone! You may argue that 'most' of your users are on iPhone, but even if, for example, 40% of your user base uses it (which I find hard to believe), that's still 60% - the majority - that don't. Issuing updates for the iPhone long before anything else, and really making a big deal of it, serves only to annoy the users of other platforms that don't have - and probably don't want - the overpriced, overhyped POS. Spotify (European music streaming service) have the same kind of philosophy, and really get flamed on their blog comments for it. It would be far better to have simultaneous releases for all platforms, and if that's not possible, at least have a beta available (even better, nightly builds as damaniac suggests), that we can try out and give useful feedback on.

I'm hoping for the new Android beta to be available for Thursday as I have a 250-mile round trip to make. Unfortunately, I'm not holding out much hope.