Posted on Facebook on August 18:Hoping any day now!
So "any day" is not tomorrowWaze Update for android will be out in about a month or so
I get the same behavior on my HTC Desire. If I click the back button it seems like there is another box of some kind behind the loading box because a single click just remove a drop shadow behind the loading box. Another back click leave me at the connect page without any possibility to enable the keyboard.damaniac wrote:Hi,
I found a little bug in the new version 1.8.99.105. If you go to the Scoreboard and try to enter your Facebook name and password it doesn't allow any text. First it takes forever with the "Loading" message and when it displays the FB screen, you can click on the fields for name and pw, but it doesn't open the on-screen keyboard and if you use the Milestone hardware keyboard you can't enter any text.
BR
damaniac
PS: Trying the alternative login screen doesn't work too.
Hadn't noticed any battery issues, but same here, exit is clean now with this version.gerben wrote:Crash on exit and battery drainage are also fixed in the new update!
Editing street properties does not work, the app crashes after pressing the confirm button.
Is this why Waze appears to be using a lot of internal storage space? 4.7M application (expected, I guess) but 2.16M of data on my Nexus One.The Fej wrote: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
Yeah, that sounds like "Nexus One Screwy ClearTouch2000". Touch one spot, registers elsewhere.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).
Oops, you beat me to it. Bingo. I almost didn't buy the N1 because of this and other problems with the touchscreen..mlangen wrote:I have had this exact same issue a few times. It's very annoying because it only happens with Waze. No other application causes this to happen.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.
Here is how I fix it most times. I lock the phone with the toplock button and then unlock it again after a couple of seconds. About 75% of the time the screen is fine. The other 25%... well that requires me having to power the phone down completely and restart it again.
Re: New Android Beta Version - 1.8.99.106