... | ... | @@ -4,20 +4,21 @@ |
|
|
|
|
|
Download release rom: https://androidfilehost.com/?w=files&flid=268615
|
|
|
|
|
|
The debug builds have Hud and Obd compiled in debug mode (can live debug them with android studio over adb connection) and the rom build.prop is set to userdebug. This also results in extra logging which may slow the unit down a little.The release build has the apk's built as release and the rom build.prop is set to user.
|
|
|
Most people will want to download the normal (release) build, not the debug one.
|
|
|
|
|
|
Unzip the chosen package on computer.
|
|
|
The debug builds have Hud and Obd compiled in debug mode (can live debug them with android studio over adb connection) and the rom build.prop is set to userdebug.
|
|
|
This also results in extra logging which may slow the unit down a little.
|
|
|
The release build has the apk's built as release and the rom build.prop is set to user.
|
|
|
|
|
|
If you're on windows and haven't used Android ADB or fastboot before, go to tools\usb_driver folder inside package and run dpinst_x64 or dpinst_x86 to install the usb driver. If you don't know whether your PC is 32 or 64 bit don't worry, try running one and if it doesn't work run the other one.
|
|
|
Unzip the chosen package on computer.
|
|
|
|
|
|
Take your navdy (not plugged into car), hold down the power button and plug it into computer with the micro usb cable in the back.
|
|
|
The navdy power light should come on red.
|
|
|
|
|
|
On windows, run FLASH_WIN to start the upgrade. If there are any errors reported post a comment here and I'll try to help.
|
|
|
Mac or Linux does work as well but hasn't been tested as much. You should be able to run FLASH_OSX_LINUX script though to start the upgrade. Linux users need to provide their sudo password for it to work.
|
|
|
If you're on windows and haven't updated the navdy rom before, start by running `WIN_INSTALL_USB_DRIVER.bat`. This should get the driver all set up.
|
|
|
|
|
|
On Windows, if it pops up saying waiting for any device it means the drivers have not assigned correctly. See this video for instructions on manually assigning the bootloader driver: https://youtu.be/8y6fDrXjEQ4.
|
|
|
If you left FLASH_WIN running in the background it should start itself, else re-run it.
|
|
|
Then run `FLASH_WIN` (if on windows) or `FLASH_OSX_LINUX.sh` (mac or linux) to start the upgrade. Linux users will need to provide a sudo password to for the tool to get access to the usb device.
|
|
|
If there are any errors reported post a comment on the reddit page and I'll try to help.
|
|
|
|
|
|
Once it's done, as long as no errors were reported on the terminal, your navdy should restart and come up on the computer as a flash drive like when plugging it in without holding power button.
|
|
|
|
... | ... | @@ -25,6 +26,14 @@ Now you can unplug it and try it in your car! |
|
|
|
|
|
The first time it starts up after flashing normally takes a long time (2 to 5 minutes) on the navdy boot screen. After that it should be back to normal.
|
|
|
|
|
|
## Troubleshooting
|
|
|
|
|
|
If you have any issues with your navdy after update, the first step should always be to run a factory reset on the display.
|
|
|
|
|
|
Plug it in to usb the same as above (power button held) but instead of running the `FLASH_*` script run `FACTORY_RESET_WIN` / `FACTORY_RESET_OSX_LINUX.sh` as appropriate. After this is finished, you should probably run the `FLASH_WIN` / `FLASH_OSX_LINUX.sh` tool again just in case.
|
|
|
|
|
|
Plug the display back into your car again. This should now boot up and go through the first-use wizard again (pairing the dial, then your phone) after which it should be back to normal. You will have lost and gauge hide settings (if you had done any) but other than that pretty much everything comes from your phone.
|
|
|
|
|
|
## RemoteOBD
|
|
|
|
|
|
This is a new feature since 3054 to allow the navdy display to be used like a wifi obd dongle, eg much like [http://www.obdlink.com/mxwf/](http://www.obdlink.com/mxwf/)
|
... | ... | |