Android beta 3.4.99.126 Feedback thread

Moderators: support, Unholy, krankyd, The Fej, perlin

Re: Android beta 3.4.99.126 Feedback thread

Postby mochrul » Mon Oct 29, 2012 9:08 am

ryanh85 wrote:When i except the location of when I am picking someone up I loose the menu button and never get a trail to follow or sometimes directions.


About loosing the menu button. I tested that if the menu button have to change (because of pick-up or you hide your position) the button is disappear. You can go to the menu if you press the hard menu button (if you have) or if you press the window where the button should be. And if you press the missing place of the menu button, the button will be appeared.
Hardware: HTC Wildfire S (Telenor), Android 2.3.5 (stock, rooted)
Software: Waze 3.5.β
Area Manager: Between Bicske and Budapest (inclusive) and Szerencs (Hungary)
Car: Ford C-MAX (blue)
mochrul
 
Posts: 210
Joined: Sun Nov 28, 2010 2:10 pm
Location: Budapest
Has thanked: 1 time
Been thanked: 1 time

Re: Android beta 3.4.99.126 Feedback thread

Postby mochrul » Mon Oct 29, 2012 9:10 am

At the first use of the waze (after upgrade to this version) the waze hard-locked. After a time have killed with the pop-up window. I sent the lock after I restarted the program (the program not recognised that something bad happened)
Hardware: HTC Wildfire S (Telenor), Android 2.3.5 (stock, rooted)
Software: Waze 3.5.β
Area Manager: Between Bicske and Budapest (inclusive) and Szerencs (Hungary)
Car: Ford C-MAX (blue)
mochrul
 
Posts: 210
Joined: Sun Nov 28, 2010 2:10 pm
Location: Budapest
Has thanked: 1 time
Been thanked: 1 time

Re: Android beta 3.4.99.126 Feedback thread

Postby deeggo » Mon Oct 29, 2012 9:50 am

Hi,

I'm still experiencing the annoying landscape-to-portrait bug: when using Waze in landscape, then hitting the Android home button, then re-maximizing Waze from the active applications, Waze will only work in portrait mode, although the device being in landscape. Only closing and restarting Waze will fix this. Also I've discovered the following: in this same forced-portrait state: I cannot click on road events on the map anymore to open the popup. So, I cannot click on a traffic jam, hazard, accident or police on the map to see what it's about. I can click on other Wazers though to get their popup. This bug is very annoying, since I always use Waze in landscape (my car dock doesn't do portrait) and do switch other applications to the foreground often, which triggers this behaviour. Please address this prior to releasing. This has only been present in the 117, 125 and 126 betas and not before that, so it shouldn't be so hard to find out what change causes this and reverse it.

The other Wazers popups often float out of the screen. This is especially the case in landscape mode, they practically always float out of the screen or at least underneath the navigation bar, making them unreadable. That navigation bar is still taking to much screen space in landscape. Please move the next turn's street name to the right of the distance to that turn, instead of the distance on top and the street name below it. There's a lot of room there and it makes perfect sense to put things next to each other in stead of on top of each other in landscape mode.

The road event popup (whether triggered automatically at standstill or being clicked on in the reports menu) still overlays the map, making it impossible to see the event and surrounding situation on the map. Please move the popup to the left and the centered map location to the right of the screen. It doesn't make sense to use a vertical orientation of things in landscape, do it horizontally, that's where the unused screen space is.

I guess in general I'm saying, give us landscape users a little bit more love please ;-) Many things are great in portrait, but need a little attention or adaptation on landscape.

The client seems a little bit more stable in the background. However reading an e-mail, opening Facebook and making a phone call was enough to make the Android kernel kill it with its current OOM value. Logs sent at 10:33 GMT+1.

Start menu is bigger in both portrait and landscape, which is great. Except, in portrait sometimes it just isn't. Sometimes it reverts back to it's old smaller size, as shown in this picture. I don't know what triggers this.
uploadfromtaptalk1351504167728.jpg
uploadfromtaptalk1351504167728.jpg (79.9 KiB) Viewed 598 times


The speed cam popup still is lost sometimes. Then only a spoken warning for the speed cam (or red light cam) is issued. No popup. Restarting the app will fix this, but it happens often.

I've tested the pickup feature in the previous 125 version. It worked great, as expected.

HTC One X, stock Android 4.0.4
Country manager Nederland & België
NL: Wiki: hoe label ik een (snel)weg correct?
HTC One X | Follow me on Twitter
Join Dropbox, free online file sync! Register through this link and give you and me 250MB extra for free. Thanks!
deeggo
Waze Champs
 
Posts: 2415
Joined: Thu Mar 04, 2010 1:21 pm
Has thanked: 54 times
Been thanked: 63 times

Re: Android beta 3.4.99.126 Feedback thread

Postby Autourdupc » Mon Oct 29, 2012 10:00 am

I have one questions concerning speed cam alerts.
If my speed is below the limit when I enter the radius of detection, I only get a pop-up alert without prompt.
If then my spped increase too much over the speed limit, do I get a TTS prompt ?
If yes, it is good.
If not, it is a bad news and so the speedcam alert should always prompt, not depending on the speed !
France - French - Galaxy S3 - Android Version 4.1.2 - Stock ROM
Translator for french language - "Localization expert"
Autourdupc
 
Posts: 728
Joined: Thu Dec 29, 2011 2:25 pm
Location: France - Lyon
Has thanked: 0 time
Been thanked: 2 times

Re: Re: Android beta 3.4.99.126 Feedback thread

Postby deeggo » Mon Oct 29, 2012 10:46 am

deeggo wrote:I'm still experiencing the annoying landscape-to-portrait bug: when using Waze in landscape, then hitting the Android home button, then re-maximizing Waze from the active applications, Waze will only work in portrait mode, although the device being in landscape. Only closing and restarting Waze will fix this. Also I've discovered the following: in this same forced-portrait state: I cannot click on road events on the map anymore to open the popup. So, I cannot click on a traffic jam, hazard, accident or police on the map to see what it's about. I can click on other Wazers though to get their popup. This bug is very annoying, since I always use Waze in landscape (my car dock doesn't do portrait) and do switch other applications to the foreground often, which triggers this behaviour. Please address this prior to releasing. This has only been present in the 117, 125 and 126 betas and not before that, so it shouldn't be so hard to find out what change causes this and reverse it.

I can now say that this has been totally solved by removing Waze with its cache and sd folder and a fresh install after that. So something was left behind from previous versions causing that problem. Anyway, I'm happy!

I did forget to mention that the splash screen is still in portrait, even if my Android home screen is landscape. The same goes voor ios BTW.
Country manager Nederland & België
NL: Wiki: hoe label ik een (snel)weg correct?
HTC One X | Follow me on Twitter
Join Dropbox, free online file sync! Register through this link and give you and me 250MB extra for free. Thanks!
deeggo
Waze Champs
 
Posts: 2415
Joined: Thu Mar 04, 2010 1:21 pm
Has thanked: 54 times
Been thanked: 63 times

Re: Android beta 3.4.99.126 Feedback thread

Postby Den_in_USA » Mon Oct 29, 2012 3:21 pm

No problems with install. However, this version is unusable for me. When I stop and the multiple popups appear, it now never returns to my actual position. I am going back to version .125 until another update.
Software Test Designer, CareFusion
T-Mobile| Dell Streak 5| Android 2.2.2
Den_in_USA
 
Posts: 97
Joined: Fri Aug 03, 2012 4:26 am
Location: Riverside, California, USA
Has thanked: 0 time
Been thanked: 0 time

Re: Android beta 3.4.99.126 Feedback thread

Postby gth33 » Mon Oct 29, 2012 3:58 pm

I went to do a map chat today, and when I placed my cursor inside the box (in preparation to type), I instead decided to press the microphone key right next to it and immediately got a notice "Message limit reached" - this popped up at the bottom of the screen before even the microphone feature could even come on and nothing had been entered into the map chat text box at all. I am running a Samsung Galaxy S III non-rooted. Hope this helps. Plz contact me if need more details. :D
gth33
 
Posts: 13
Joined: Fri Sep 03, 2010 2:29 am
Has thanked: 0 time
Been thanked: 0 time

Re: Android beta 3.4.99.126 Feedback thread

Postby wimdelange » Mon Oct 29, 2012 5:01 pm

Not sure what happened, but when I drove to home, I saw the finish flag on the correct location, but Waze was telling me to drive to a location a 100 meter to the south. Even when I was in the segment before my home, it was telling to to that wrong location. I'll check the maps, but as far as I know there was no INTL map update this weekend? Or was it.

Nope, map looks fine. Hope that it is not the client? Anything I can do when it happens again?
Groetjes,
Wim de Lange
Area Manager Zoetermeer
HTC Sensation Android 4.0.1
Waze beta 3.5.1.904
wimdelange
 
Posts: 105
Joined: Sat May 05, 2012 4:21 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Android beta 3.4.99.126 Feedback thread

Postby crazed_out » Mon Oct 29, 2012 5:33 pm

Bug or strange and unexpected behaviour in routing occured driving home from work today. In the.125 beta I added home as my finish, selected a different route than the fastest. Then added a stop in another direction than my general direction home, to pick up family. Once again selected "Routes" to get another route than the first selected. My drive home is about 30 minutes and with the extra stop at least another 20 minutes or so. ETA was displayed as 1 min to stop, which I later realised hadn't been selected but ignored while selecting the other route. Stopped at a bus stop and reentered the routing again doing it in exactly the same way. Same problem occured again. Then I inserted the stop without selecting an alternative route. Everything worked as expected.

I think that when selecting to find an alternative route when navigating with a stop Waze doesn't understand that I want an alternative route to my stop but instead checks for routes to my final destination. The navigation was directing me home instead of via the other place I was going. Strange though with the ETA 1 min.

Will try this frequently in betas to come.

Edit: This was on a Samsung Galaxy note running Android 4.0.4.

Cheers
crazed_out
Area Manager in Sweden, parts of Västra Götaland (West Sweden).
Samsung Galaxy Note II GT-N7105 (4.1.2 stock) | HTC Desire HD (2.3.5 stock) | Volvo 850 T5 -96 med +25000mil på mätaren.
crazed_out
 
Posts: 124
Joined: Wed Feb 08, 2012 9:24 am
Has thanked: 4 times
Been thanked: 2 times

Re: Android beta 3.4.99.126 Feedback thread

Postby henslok » Mon Oct 29, 2012 5:50 pm

Installed okay, and let me guess: it changed from miles yo km again.

Sent from my GT-I9100 using Tapatalk 2
henslok
 
Posts: 33
Joined: Tue Dec 22, 2009 9:20 pm
Has thanked: 0 time
Been thanked: 1 time

PreviousNext

Return to App Beta Testing

Who is online

Users browsing this forum: No registered users