antlane

There is an open bug about this on the Waze beta testing site. I've added some comments to try to encourage them to fix it sooner rather than later.

I think I've got to the bottom of why my phone kept crashing when I pressed the home button. It seems it was down to me using PluggedIn to autolaunch Waze. I tried launching other AppRadio apps like ECTouch, CarMediaPlayer etc. and had the same problems. If I disabled PluggedIn and launched those apps manually, the crashing stopped. So instead, now I'm using Activator to unlock the phone and launch Waze when the phone is plugged in (the new Activator allows more than one action). However, I've also had to disable FlipSwitch (which the latest versions of Activator install automatically) ot

Ever since I upgraded to the latest beta, my phone freezes up each time I connect it for the first time on a journey. After a few minutes, it eventually reboots and when I finally get to the App screen, all the native apps aren't visible (only the non-native apps I've enabled through AppEx appear). I then have to disconnect and reconnect the phone to get the native apps to appear. Also, the AppRadio app's count of new apps keeps resetting. Is anyone else having these problems? I'll try downgrading to the last beta (the iphone5 test version) to see if this solves the error.

Sorry for the typo, it should have read 1600x900. I didn't have a chance to play for that long but it did seem quite exact from what I could tell.

Window: 0.000000 0.000000 1600.000000 90.000000 Appframe: 64.000000 36.000000 1152.000000 648.000000 I assume you've hardcoded the 0.9 multiplier in now as I had to set the X and Y multipliers to 1.0 to get the calibration right. Not sure if it's been reported before but the framerate on unsupported apps seems quite slow. The map on TomTom seems to refresh much slower than on the phone screen although it's difficult to tell when driving.

I can confirm that setting the Y multiplier to 0.9 solves the calibration issues for landscape apps. Not sure how considering there were issues with both the X and Y axes but not complaining! For portrait apps, I needed to reset the Y multiplier to 1.0 Finally, the debug values that were displayed within the AppRadio app were: View transform: 1.000000, 1.000000 View size: 908.000000, 480.000000 Resolution: 1280.000000, 720.000000 Thanks for getting this sorted!

Great stuff - look forward to it!

Hi Mike, Here's what I've found with the latest version and my iPhone5. Notifications now work and they're really useful! Unfortunately, calibration is now way-off. Here's a list of places I've pressed and what actually registers. Top-left back button = fine Top-right cancel button = doesn't register at all Further down = presses are registering higher than I'm touching shift key = q z = w x = e c = e v = r b = r n = t m = t backspace = y 123 = a keyboard selector (image of globe) = a microphone = s spacebar (depending on where you press) = s, d, f or g search = h C

Double post - sorry

Ahhh, I misunderstood the request - I thought Mike wanted to see the coordinates to be able to work out how far the calibration was off.

But then I can't do a video for you to help you coordinate the iPhone 5

I'm unable to launch an app to be able to do this as the beta displays the touch coordinate but then doesn't do anything else. If you can fix this, I'll then make a video. Or will doing a video of a supported app be ok?

Here are my results using the file Mike linked to on his DropBox (using an sph-DA100 + iPhone 5) Top-left: 19.180273, 5.998718 Top-right: 1270.390381, 7.492905 Bottom-left: 4.765770,698.993469 Bottom-right: 1271.991943, 698.993469 There looks to be an inconsistency between the top-left and top-right so I can do them again if necessary. My cycript output when using the AppRadio app can be found here: http://pastebin.com/aMRY4y5p And the output when using Google Maps: http://pastebin.com/GDV4TkRb Hope this helps get decent calibration!

While we're on the subject of requests, just in case this was missed, could this be implemented too?

Yes, I think it should be an option - it shouldn't be forced on people.