The magic tree Points an skip Waypoints during navigation

[Corjan Meijerink]

@Brian-McG Our "skip waypoint" function was implemented before they had the firmware to support the "app switching" feature (I believe).

I can extremely easily move it to another function which will simply mean another function disappears. It was mapped to DC right because that is intuitive for a "skip waypoint" as right kinda implies "next".

DC down = Toggle ETA
DC left = Compass (this one you definitely need)
DC up = Open menu (but broken since another firmware 2.x update)

I guess we can switch "toggle ETA" and "skip waypoint".

But bluetooth controllers do kinda frustrate me sometimes. SilverFox and Carpe Iter communicate their changes but others absolutely not

Functions work and then they are broken because their firmware changes and other keycodes are sent. Demonstrated by the fact that open menu does not work anymore (or it might again) with the Remotek One.

So yeah, if actual remotek users tell me what DC they want to sacrifice (I guess toggle ETA is the only option), I can definitely make that change.

[Dave J 0]

@Corjan-Meijerink I like it just the way the key mapping is at the moment for the Remotek One. I have no need for the app switching as I am on iOS.

[Brian McG]

@Brian-McG Our "skip waypoint" function was implemented before they had the firmware to support the "app switching" feature (I believe). >

I believe the reserved key DC right to switch app function has been in the Remotek firmware from day one, I know the MRA implementation of the DC right broke the Remotek switch function

will simply mean another function disappears.....what DC they want to sacrifice>

Why, does the skip function have to be a DC, is it not possible to map a key to a longpress?

[Corjan Meijerink]

@Brian-McG then I might have simply never used their custom app and just looked at the documentation. But still, not the real point here.

There are no long presses for the remotek.
If so, they need to update their manuals / communicate with people implementing their controllers.

With the hardness of the buttons on a remotek I’m always impressed that people can execute a DC while driving with gloves

[Hubert Thoring]

I use the following old version V1.1.2 which can still be loaded for MyRouteApp users...

I am an iOS user - with the Remotek One forapprox. 2 years https://forum.myrouteapp.com/post/70445

With the old V1.1.2 of the Remotek One, therare two important levels:

Navigate:

• Zooming +/-
• Skip WP

Profile change:

• APP switching with DCH1 between the profiles with button ( 1 )
• 1.) App MRA (Map Profile)
• 2.) App Spotify or another app (as media profile)

Switching is possible via iOS shortcut...

[Dave J 0]

@Hubert-Thoring I use the latest firmware (V2.1.0) for the Remotek and the profile functionality is still there. It all works well for me with iOS and I am a happy user. I have an Android phone as well and there are more options for configurability with Android than iOS so I can understand the loss of options. That said, I do not want to lose the current set up of buttons of DC left, right and down.

@Corjan-Meijerink There is a new version of the firmware coming ‘soon’ although that was muted at least a couple of months ago. Users should be able to ‘program’ buttons to their need with this forthcoming version of the firmware although there was not a lot of information given. I will probably have to contact Remotek again once the firmware is released if the MRA configuration is not workable. As far as usability and DC, the angle of the device is key and I had a wide angle left bracket template from the Remotek website 3D printed - really helps.

[Graziano 0]

@Corjan-Meijerink said in The magic tree Points an skip Waypoints during navigation:

So yeah, if actual remotek users tell me what DC they want to sacrifice (I guess toggle ETA is the only option), I can definitely make that change.

Please don't, toggle ETA is a super useful feature

[Corjan Meijerink]

@Graziano-0 agree

[Brian McG]

I also agree that there should be no sacrifice of existing functionality
(I just want to have my cake & eat it, to have the Remotek app toggling functionality back & have the skip point function as well))

"DC down = Toggle ETA" is extremely useful, I am regularly toggling this to see time to next Via point & time to final destination

"DC left = Compass (this one you definitely need)" is 200% needed to re-centre the map after any panning of the map

"DC up = Open menu (but broken since another firmware 2.x update)" I do not understand why this is marked as does not work with 2.x, I have Remotek version 2.1.0 installed & "DC up" in navigation mode does exactly as specified, it opens the menu & always has done so, maybe only a 2.0 issue

Now "DC Right" is a bit more complex
For me on Android 12 I have the option/ability via the Remotek app to enable the Android "Accessibility Service"
When the "Accessibility Service" is enabled I believe this gives the Remotek the permission/ability to perform the app switching function so I can use the great Remotek feature "DC right" to toggle & click through a list of preselected apps
When the "Accessibility Service" is disabled I can use only use "DC Right" to perform the MRA designated skip function

So because MRA chose the "DC right" key combination for the skip function it effectively replaces the one key combination that Remotek had reserved
I cannot therefore have both the MRA skip function & Remotek app toggling function at the same time

As for the hardness of the buttons, yes it does require a positive pressure but this just takes practice & familiarity, we all know that with practice things get easier / better

As for "no longpress" for the Remotek I think this may be an incorrect statement
If I take the android app "Key Mapper"

I can set it up so that it recognises a "longpress down" as a trigger to send the command M so that within MRA a skip action is performed,
So I do believe it should be possible for MRA to edit the Remotek profile in the MRA Navigation App to recognise a longpress

As for documentation it looks like the Remotek is capable of a bewildering number of key combinations
"SC – SingleClick
DC – Double Click
H – Push down and hold button (this is equivalent to longpress )
SCH1 – Single Click Hold – One click and let go, then immediately push down the same button and hold it for duration(Dur), example; SCH1 is Single Click Hold for 1 second.
DCH2 – Double Click Hold – Two clicks followed by hold for a duration, here 2 seconds"
The above info from this MRA thread

I admit some of these combinations would take a lot of practice using motorbike gloves but there are certainly plenty of key combinations available for the skip function without it having to overwrite the Remotek Toggle feature

[Hubert Thoring]

But then please with an additional good solution with an input settings selection for further Remotek One solutions or how is that supposed to work?!

• Remotek One V1.x / V2.x

• Remotek One V2.1.1 Brain McGAndroid