Is there any chance that if you hold in the Navi button for a few seconds (instead of just pressing it) that it will switch between the Navi and 2DIN functions? I still say that we need to find a way to switch between 2DIN/Navi. Or maybe try holding in the Radio button while in Navi to switch back to 2DIN? Just trying to think of some other possible ways to switch back and forth....
I have tried all types of combinations regarding the buttons around the unit and none of them take me out of the Navi screen.
There is one thing i haven't tried yet is using the remote control unit to exit, i'll try that tonight and see if it might work.
Boki_Srb, can you let me know where i can find this ''package adapted to such device. Primo ESX 9.6.5.278914.''
A direct link would be greatly appreciated.
Thanks
...
Boki_Srb, can you let me know where i can find this ''package adapted to such device. Primo ESX 9.6.5.278914.''
A direct link would be greatly appreciated.
...
Here it is, fresh uploaded:
Spoiler: dl
This post requires you to click the "LIKE this post" button and hit F5 to read this content.
P.S.
Sometimes, you just have to try several versions.
If this don't work, good versuion is also 9.6.5.306142, not dedicated, but who knows...
Always try with clean setup on clean SD card, they are cheap, that you receive from the seller leave aside.
Btw, what is exact model you have, ALYVAT VW-6501 precise?
I read several feedbeck from other buyers, all complain of the same problem. So, it is up to device, let see if can be fixed.
If Primo definitely stuck, try with NextGen: [Only registered and activated users can see links. ]
or [Only registered and activated users can see links. ]
or [Only registered and activated users can see links. ]
or, you can live without exit button Just turn off device.
Last edited by Boki; 16th May 2017 at 10:07 AM.
Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search. NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click! [Only registered and activated users can see links. ] <- Click!
Spoiler: obs
Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.
P.S.
Sometimes, you just have to try several versions.
If this don't work, good versuion is also 9.6.5.306142, not dedicated, but who knows...
Always try with clean setup on clean SD card, they are cheap, that you receive from the seller leave aside.
Btw, what is exact model you have, ALYVAT VW-6501 precise?
I read several feedbeck from other buyers, all complain of the same problem. So, it is up to device, let see if can be fixed.
If Primo definitely stuck, try with NextGen: [Only registered and activated users can see links. ]
or [Only registered and activated users can see links. ]
or [Only registered and activated users can see links. ]
or, you can live without exit button Just turn off device.
I will try them and see if any of them work, will report shortly.
Well i tested both versions as suggested by Boki_Srb and again the program loads perfectly and everything works great except for the EXIT feature, i'm liking Jtrosky's theory more and more since all other options with the IGO Primo's software doesn't seem to be the issue.
Let me know what else i can try!
Is there any chance that if you hold in the Navi button for a few seconds (instead of just pressing it) that it will switch between the Navi and 2DIN functions? I still say that we need to find a way to switch between 2DIN/Navi. Or maybe try holding in the Radio button while in Navi to switch back to 2DIN? Just trying to think of some other possible ways to switch back and forth....
Sent from my Vi10 Plus using Tapatalk
I was wondering about that as well; but I think if the keycode of the button pressed can be determined, then proggy might be able to be config to do something with it. This is why I asked the proggy to be run and keycode collected.
Do not PM me with questions. That's what a forum is for.
I was wondering about that as well; but I think if the keycode of the button pressed can be determined, then proggy might be able to be config to do something with it. This is why I asked the proggy to be run and keycode collected.
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.
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.
Do not PM me with questions. That's what a forum is for.
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.
The problem is that the iGo Minimize function doesn't work either (it does the same thing that the Exit function does). From an earlier post:
"Jtrosky there is a minimize button but when I click on it the button turns yellow and nothing happens, it goes no where..."
So whether he minimizes Primo with the software button or a hardware button, I don't think that the result will be any different (but I could be wrong). it seems to me that the Primo software is cut off from the rest of the 2DIN system at the OS level (like it is on my Rosen GM1010). With the Rosen, even if I run a task manager on the Navi "side", there are no other processes running - it runs in it's own dedicated WinCE OS. I have a feeling that his Navigation function is completely self-contained like it is on my Rosen - which would require a way to switch between 2DIN and Navi functions (controlled by the 2DIN, not Primo). But we can't seem to get that to happen...
Bookmarks