BMW Carpe Iter control hub select function

[Mark Hamilton 0]

@Corjan-Meijerink
Top man, thanks for the quick reply. I’ll check 4.3.3 when released and feedback.

[Mark Hamilton 0]

@Corjan-Meijerink
Hi Corjan. I have used the tablet today with 4.3.3 357 and there doesn’t appear to be any improvement on control functions. Hopefully this will be resolved with 4.3.4.
I also miss the panning functionality that you get within Google maps etc using this controller and I also had this with MRA using BarButtons is this going to be possible with the CI BMW controller as for me panning is used more than say menu items or skipping? Tapping vs long press for more functionality maybe..
I have the full Controller set including the hub and extra 4 buttons

[Corjan Meijerink]

@Mark-Hamilton-0 Sorry, there is a slight delay in getting our hands on a test device. I'll also reach out to Carpe Iter again to check with them about the expected controls. As of now, no changes yet made for 4.3.4.

Panning is indeed not possible with this controller.
The arrow functions got different functionalities attached.
https://support.myrouteapp.com/en/support/solutions/articles/12000100670-bluetooth-controllers

[Mark Hamilton 0]

@Corjan-Meijerink
I’m assuming you mean the CI BMW controller can’t pan within MRA as it does pan with Google Maps, Waze, Locus, DMD2, so the functionality is there just not chosen to do this with the buttons within MRA set up? In my view the panning function is used more when navigating than the current button functions.
The links from the Manual controllers sections seem like they don’t work, I get ‘Page you were looking for doesn’t exist’! When selecting the individual controller sections.

[Mark Hamilton 0]

@Corjan-Meijerink hello Corjan, is there any update on when this controller (including buttons) will work correctly with MyRouteapp? I did try 4.3.4 with no improvement. I haven’t tried the recent 4.3.5 beta release but it seemed the only change in that was Here SDK.

[Corjan Meijerink]

@Mark-Hamilton-0 I've been in touch with them and the working should be correct. I've requested them to test it too.

If you still experience issues, could you also contact them?
Feel free to add corjan@myrouteapp.com in the cc.

I believe there have been some changes regarding direct communication or using the Carpe Control App.

[Mark Hamilton 0]

@Corjan-Meijerink Hi Corjan, thanks for the response. I have tested again today and the situation is better but not fully working. Please view the below and let me know if you think I should still raise with Carpe Iter for them to resolve.

Wizz wheel
Up - Zoom in works / will move to next menu item
Down - Zoom out works / will move to previous menu item
Right - Camera cycle works / SELECT MENU ITEM NOT WORKING

Four buttons on right throttle twist.

Right - START ROUTE NOT WORKING / Skip waypoint works
Left - Toggle ETA information working well
Up - Fit route to map works
Down - Open close menu works.

[Corjan Meijerink]

@Mark-Hamilton-0 Thanks!

I've made some immediate changes that will be available in the next beta version 4.3.6 (380).

The select menu should be working! Something was indeed missing there.

The start routing already work I believe (as the skip waypoint works too) but you do need to have a route "open" on the home screen.

[Mark Hamilton 0]

@Corjan-Meijerink hi Corjan thanks for the changes. Hopefully that will solve the issues.

I only have beta access to IOS version and obviously Carpe Iter needs Android so unless I can get beta access to Android I’ll have to wait for full release of 4.3.6 to test again?

[Corjan Meijerink]

@Mark-Hamilton-0 If you create a support ticket (myrouteapp.com/support) where you mention me and this forum conversation you can request beta access for Android too.

Save me one email and already share you google mail that you use on that phone I will then add you to the beta program for Android too.

[Mark Hamilton 0]

@Corjan-Meijerink hi Corjan, I’ve tested this today using Android beta 4.3.6 381 and can confirm all functions are working as intended. Thank you for making these changes.

[Corjan Meijerink]

@Mark-Hamilton-0 Awesome!