Thread: Chinese 2 DIN radio/GPS, will not exit GPS mode

Originally Posted by jtrosky

My understanding with the keycodes (and associated [keybind] section in sys.txt/device .ini files) was that they allow you to "program" a 2DIN hardware key to perform an iGo software function (so that, for example, you can program a hardware key to bring up the Primo "Find" dialog). In this case, we need to initiate a 2DIN function though (to switch back to the main 2DIN interface), so I'm not sure how the key binding can help in this case - unless I'm just not understanding the approach you are taking with the keybindings.

In other words, I was under the impression that setting up keybindings in iGo just allows us to map a software function to a hardware key - not map a hardware function to a hardware key. If that makes sense... :-) At least not without a version of Primo that is customized to this specific hardware.

In my mind, the real issue here is that the 2DIN is not allowing us to switch between 2DIN and Navi functions. As far as I can tell, Primo itself is operating 100% correctly and there is nothing to "fix" on the Primo side.

Just thinking out loud....

Sent from my Vi10 Plus using Tapatalk

The objective is to make proggy does something if hardware key is pressed (at least that's what I thought it is.) There is an event to minimize proggy which might get him back to main menu of nav unit (not proggy) So if we can find the keycode of a key and bind to that event, it should do it.

@newbeegps - Just one more thing (maybe it does not matter, but...): Why is ALPINE EXITING LOGO on it?
My package is totally unbranded, and only for 800 res.

I can't speak for that "function", I was referring to the minimize event. And you might be correct that "minimize" is blocked (not handled) and doesn't work. I know under android it doesn't. There is nothing to loose by trying. If indeed all events are not handled, then we will definitely know when we bind one of the key to an event that I know works.

Out of curiosity, I just tried the WinCE keymapper utility on my Rosen GM1010 2DIN - unfortunately, on this 2DIN, the program doesn't capture any of the hardware keys - they simply perform their original function when pressed while running the utility. I guess that the navigation OS on my unit has no access to those keys at all (since navi is running in it's own "isolated" OS). I'll try it on a GM1210 soon just to see what happens (I have a GM1010, GM1210 and an Advent OGM-1 setup on the bench for testing/setup as I sell them to other Impala owners).

EDIT: keymapper utility doesn't work on GM1210 either... I'm assuming that you just run it and press the keys while it's running and it's supposed to show the keycodes... Maybe it's meant more for "single function" PNA's and just doesn't work on 2DINs? Not sure...

Sent from my Vi10 Plus using Tapatalk

I have no idea if/how the WinCE keymapper works (it was suggested by someone else) I would love to play with it but since I don't have access to WinCE at the moment, I can't. I wonder if it works on PNA WinCE devices. On PDA people like to do minimized, but on PNA (and maybe DIN) not so much. That doesn't mean it won't work; and as I said, it's worth trying.

Originally Posted by jtrosky

Yeah, I wish I had a WinCE PNA to try it on as well... Unfortunately, the only WinCE PNA device that I have (SUPER old) doesn't have *any* physical buttons. :-)

That being said, I'll connect my Advent OGM-1 2DIN up later and mess with it, because I know that the Advent actually uses a keybind config for one of it's physical keys (only one I've seen use the keybind config) - so I have a feeling that the utility might work on that one. I'll report my findings.

Sent from my Vi10 Plus using Tapatalk

Interestingly, the WinCE keycode capture utility didn't work on my Advent OGM-1 either (which actually uses the keybind feature to map a hardware "Dest" key to the Primo "Enter destination" screen (which does work).

Strange - not sure why that app isn't working with any of the WinCE 2DIN's I've tried it on (one running WinCE 5 and two running WinCE 6).

EDIT: I don't think the app works like I expected (but not sure how it works yet either)... Will keep messing with it.

Sent from my Vi10 Plus using Tapatalk