Remotek-one firmware 2.0.0

[Corjan Meijerink]

@Hubert-Thoring pdf is not possible.
Glad it all works as intended

[Hubert Thoring]

@Stanisław
@Dave-J-0
@Brian-McG
@Corjan-Meijerink

For your information:
This now works as described in the appendix, after the new MRA update V 4.3.6 with the Remotek One V 1.1.2.

a translation into English ....

[Stanisław]

I tested Remotek-one yesterday with new android tablet and +/- buttons don't work properly, no zoom but panning instead of it. Tested with both 2.1 and 1.1.2 firmware versions, with the phone the same. Could anyone confirm that it is a problem of the new version of MRA?

[Corjan Meijerink]

@Stanisław Have you selected Remotek One as input device in MRA?

[Stanisław]

@Corjan-Meijerink yes, of course, and before it worked correctly with firmware 1.1.2. What's more - zooming does work on initial screen with the map but not in the navigation mode, that's why I suppose it can be related to the recent changes in the app.

[Corjan Meijerink]

@Stanisław hmm no clue then.
As discussed in this thread, it all worked as intended and we haven’t changed anything regarding this.

Maybe @Hubert-Thoring can test his.

[Hubert Thoring]

@Stanisław
@Corjan-Meijerink

So, everything is going very well for me since the V4.3.6 also more than zooming and panning the map, the same applies to the latest app V4.3.8 still exactly as described in the previous list here in the thread.

Note: I use iOS with an iPhone Xr with the old Remotek One version 1.x.x as delivered in 6.6.2024. I have no indication of the version, for that I would need an Android phone and the Remotek One app which is not available for iOS.

Important: with iOS iPhone mobile phone

• Keyboard Control Off

• Input keyboard on Remotek

• Set Remotek One to iOS

I can only give my support for iOS / iPhone application.

Best regards Hubert

[Hubert Thoring]

@Stanisław
@Corjan-Meijerink

Here's a video, for a better view, it works more than well for me

Link zum Video von Remotek One und MRA V4.3.8

[Stanisław]

@Hubert-Thoring Thank you for the video. I have checked once more and found the reason, I have just uninstalled the Remotek application now and it started to work - I mean zoom. What's more, in this case right doubleclick works as skip next waypoint, with application installed it was covered by switching to another application, set up in the settings. So it is almost good now. The only problem I can see is switching to the top view mode by zooming or panning. It is quite strange and afterwords I can not go back to the dynamic mode using left doubleclick. It is quite random, I will test it more and check if it is a real problem.

[Martin Wilcke]

Exactly the same experience here. With the Remotek app installed, zoom in/out works on the overview map, but not when navigating (panning up/down instead). With the app uninstalled, zooming works when navigating as well. The only downside is the missing DC right to switch apps, but that's acceptable.

Thanks @Stanisław for this tip - I would never have thought of that by myself!

[TenWheels]

The exact same thing happens to me. When I enable the Accessibility service in the Remotek app, the remote control no longer responds as expected while driving a route. I will send an email to Remotek with my findings. With the Accessibility service disabled, switching between the two profiles no longer works.

Android 14, Remotek firmware 2.1.0, MRA 4.3.8

[Martin Wilcke]

@TenWheels said in Remotek-one firmware 2.0.0:

When I enable the Accessibility service in the Remotek app, the remote control no longer responds as expected while driving a route. I will send an email to Remotek with my findings.

But the question is whether a change in the Remotek app is helpful because zoom in/out works in the MRA overview map; the problem only occurs during navigation. Obviously, MRA interprets the keyboard codes sent by the controller differently.

[Jörgen]

@Martin-Wilcke open an editor and push the Remotek button to see which code (which letter) is send, that helps to see problems.

[Martin Wilcke]

@Jörgen said in Remotek-one firmware 2.0.0:

open an editor and push the Remotek button to see which code (which letter) is send, that helps to see problems.

Yes, that can be done. But this shows the codes that are sent directly from the controller. However, the problem discussed here only arises if the Remotek app is activated and intercepts and modifies the codes sent.

I would have to place the app between the controller and the editor to see this, but I don't know how.

But I'm not seeking this any further because I don't care. I use the controller without the Remotek app activated anyway because without the app, DC3 (double-click on button 3) skips the upcoming route point, which I like to use. With the Remotek app activated, DC3 switches between configurable apps (e.g. MRA and Google Maps), which I don't need.

[TenWheels]

Remotek has just released an update on the Play Store, and now the remote control works as intended. I'm happy about it!

It's wonderful when a software issue is addressed quickly and effectively. It makes life so much easier

[Martin Wilcke]

@TenWheels

Excellent news! Will give it a try later…

[Hubert Thoring]

@Corjan-Meijerink
@TenWheels
@Stanisław
@Brian-McG
@Dave-J-0
@Martin-Wilcke

Hey Corjan, I have to ask again here, because it only crashes with the really best MyRouteApp for me as described below with the MRA navigation. All other apps such as GuRuMaps, Kurver, Google Maps, etc. have no problem with this.

I turn off the keyboard control in the MRA navigation, but actually I could use even more Remotek One functions, such as switching between two apps in the test. That's exactly what I'm missing because I compare MRA with curvy, sorry I just like to test, ... Don't worry I like MRA better.!

Starting point:

Base: iOS, iPhone Xr and then the accessibility in iOS with activated keyboard control .... and the Remotek One.

Can operate the normal MRA app but in the MRA navigation the MRA app always crashes after a short time, as already described elsewhere in the past. Can there perhaps be an MRA reason because the other users here also have problems with the Remotek app on Android ... or am I the only iPhone iOS user in the application here.

VG

———————

Hey Corjan, ich muss hier noch einmal fragen, da es bei mir nur bei der wirklich für mich besten MyRouteApp so wie untern beschrieben weiterhin mit der MRA Navigation zum Absturz kommt. Alle anderen Apps wie GuRuMaps, Kurviger, Google Maps usw. haben damit kein Problem.

Ich schalte bei der MRA Navigation die Tastatursteuerung aus, aber eigentlich könnte ich noch mehr Remotek One Funktionen nutzen wie zum Beispiel zwischen zwei Apps im Test zu wechseln. Genau das fehlt mir gerade weil ich MRA mit Kurviger vergleiche, sorry ich teste halt gerne, … Keine Angst MRA gefällt mir besser.!

Ausgangsbasis:

Basis: iOS, iPhone Xr und dann die Bedienungshilfe im iOS mit eingeschaltete Tastatursteuerung …. und der Remotek One.

Kann die normale MRA App bedienen aber in der MRA Navigation stürzt die MRA App immer nach kurzer Zeit ab, wie schon in der Vergangenheit an anderer Stelle beschrieben. Kann es doch vielleicht einen MRA Grund geben da es bei den anderen Anwendern hier ja auch Probleme mit der Remotek App unter Android gibt … oder bin ich hier der einzige iPhone iOS User in der Anwendung.

VG

[Hubert Thoring]

@Corjan-Meijerink
@TenWheels
@Stanisław
@Brian-McG
@Dave-J-0
@Martin-Wilcke

Sorry, have to correct it again and correct it here. I made a mistake with the order in the last post, just tested it again and tried.

• If you start the MRA with the iOS setting under Accessibility "Keyboard Control On" and paired Remotek One, the current app version 4.3.8 (386) crashes directly.

• If you start the MRA with the iOS setting under accessibility "Keyboard control on" and leave Bluetooth off beforehand, i.e. without the Remotek One being paired, then the MAR starts normally, then you go to the navigation and then turn on the first Bluetooth on couples the Remotek One and all functions of the Remotek One and the MRA functions work perfectly. When leaving the MRA navigation, the MRA then crashes again.

Conclusion:

The normal MyRouteApp in the Start App menu application does not support iOS user aids with a switched on "keyboard control on" under iOS, only in the MRA navigation level of the app it is then flawless, with the possible functions that can be performed well with the Remotek One and the MRA navigation.

• Switching between two apps here MRA and a radio player only works with "Keyboard Control On".

• With "Keyboard Control Off" the entire MyRouteApp goes without crashing, but switching between the two apps is no longer possible.

VG

—————-

Sorry, muss es noch einmal richtigstellen und hier korrigieren. Ich habe mich im letzten Beitrag vertan mit der Reihenfolge, habe es gerade noch einmal getestet und versucht.

• Startet man die MRA mit der iOS Einstellung unter Bedienungshilfe „Tastatursteuerung Ein“ und gekoppelter Remotek One, dann stürzt die jetzige App Version 4.3.8 (386) direkt ab.

• Startet man die MRA mit der iOS Einstellung unter Bedienungshilfe „Tastatursteuerung Ein“ und lässt vorher Bluetooth Aus, also ohne das die Remotek One gekoppelt ist, dann startet die MAR normal, geht man dann in die Navigation und schaltet dann erste Bluetooth Ein koppelt die Remotek One und alle Funktionen der Remotek One und der MRA Funktionen gehen einwandfrei. Beim verlassen der MRA Navigation stürzt die MRA dann wieder ab.

Fazit:
Die normale MyRouteApp im der Start App Menü Anwendung verträgt keine iOS Bedienhilfen mit einer eingeschalteten „Tastatursteuerung Ein“ unter iOS, erst in der MRA Navigationsebene der App geht es dann fehlerfrei, mit den möglichen Funktionen die sich mit der Remotek One und der MRA Navigation gut ausführen lassen.

• Das Umschalten zwischen zwei Apps hier MRA und einem Radioplayer geht nur mit „Tastatursteuerung Ein“.

• Mit „Tastatursteuerung Aus“ geht die gesamte MyRouteApp ohne Absturz, jedoch das umschalten zwischen den zwei Apps geht dann nicht mehr.

VG