Found the problem. Had to make the following change in ui.h under the #elif MOTHERBOARD == 37 // UltiMaker 1.5.7#define UI_DISPLAY_D7_PIN      6

Thanks repetier. It is the 20x4 controller. I'm still using the non-dev firmware 92.9 maybe? Should I just change the uiconfig.h here? #define UI_LCD_WIDTH 128

Then I tried changing #define UI_DISPLAY_CHARSET to different numbers-still no luck.

#define ALWAYS_CHECK_ENDSTOPS 0

#define ENDSTOP_X2_MIN_ID 1

#define UI_STATUS_RAM(status) uid.setStatus(status);

#define UI_STATUS(status) uid.setStatusP(PSTR(status));

 #define  _WRITE(IO, v)   do { if (v) {DIO ##  IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ##  IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)

#define X_HOME_DIR 1

#define ENDSTOP_Z_BACK_ON_HOME 1

#define ENDSTOP_Z_BACK_ON_HOME 1

#define DELTA_PROBEABLE_RADIUS (DELTA_PRINTABLE_RADIUS - 40)

You have the very special case of max and min z endstop. That seems confusing for the firmware as it takes routines meant for z max homing like computing the z length from distance to top, while negle

#define CONFIGURATION_H

At least I have seen the LCD command doing XYZ, while we set the configuration.h as YXZ: "#define HOMING_ORDER HOME_ORDER_YXZ"

#define ENDSTOP_PULLUP false // ?????

#define XAXIS_STEPS_PER_MM 66.5  //nema17 1.8 degree

Tried with #define FEATURE_WATCHDOG 1 and 0 in configuration.h no difference.

#define ZHOME_X_POS 999999

It is not a display issue. It is the encoder sending switch signals. I assume your display has a slower encode as the set#define UI_ENCODER_SPEED 1