What I have found is that the skin works with the plugin (mobilephone.net) as long as it is set up right. If I were you, I would go to lambo's thread and see if he can help you.
WebBrowser in skin.ini -----> WebBrowser in Exectbl.ini -----> FENNEC
FENNEC in Exectbl.ini -----> fennec path
If I put in Skin.ini
there is something strange, isn't it?
RideRunner now loads the plugins that are installed in that folder by default.
The old DFX4 would have had plugins listed in the menu.skin (or a separate file which was included (INC) in the menu.skin), RideRunner (or RoadRunner) would then have loaded those plugins from anywhere as long as they were registered.
DFX5 now takes advantage of RideRunners ability to load the plugins from the plugins folder automatically to dispense with that list in the menu.skin.
Solution 1. (preferred)
Move the TMS plugin to RideRunners plugin folder and register the DLL.
Add x,tms to the menu.skin of DFX
TMS skin looks fine to me. Compared it to my iDrive one (which I know works) and the labels etc have the same codes.
Thanks for the confirmation Enforcer. I did use the same labels as his skin, but you never know about typo's and such when you can not physically test it.
As for the phone questions, I personally use a hardware device made by parrot for phone in the car. I find that setting up a phone with the blue tooth and all is a royal pain, and never is 100% rock solid.
The skin is provided, and has been tested to work, so as others suggested, I would check the MobilePhone.net thread.
with this line:Code:
I also noticed this in the menu.ini of the DFX/Plugins/RRVoice folder.Code:
I am pretty sure that the 2nd Scroll Up should be replaced with Page Up.Code: