Remotek-one firmware 2.0.0
-
@Hubert-Thoring pdf is not possible.
Glad it all works as intended -
@Stanisław
@Dave-J-0
@Brian-McG
@Corjan-MeijerinkFor 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 ....
-
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?
-
@Stanisław Have you selected Remotek One as input device in MRA?
-
@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.
-
@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.
-
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
-
-
Here's a video, for a better view, it works more than well for me
-
@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.
-
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!
-
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
-
@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.
-
@Martin-Wilcke open an editor and push the Remotek button to see which code (which letter) is send, that helps to see problems.
-
@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.
-
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
-
Excellent news! Will give it a try later…