@ Dave McLaughlin - I just looked again and I can see I was wrong. I just assumed that the display module would have all required components installed. Another lesson learned.
Unfortunately to test with resistors I’ll have to wait at least 8 hours.
What can I say. I don’t have much hardware experience. But I will 
I made the same mistake trying that without the pullups, because I was blinded by the picture on the Display-NHVN-page ;)… I just took a Gadgeteer-breakout to connect them via the I-socket on the displayboard.
Thank you @ Dave McLaughlin 
and all who helped! It was indeed a pull ups issue, I completely forgot about them as the same setup was working Cobra III. This is not my first time working with I2C and I should of remember to check for resistors.
I put 4.7k pull ups and it looks to me that touch works hell a lot smoother than the built in 2.2k on Cobra III. On Cobra its not always response on the first tap.
:dance:
Well, nothing for production or something critical, but for my development needs, this little guy did it 
1 Like
I’ve found that G120 can be a little slow to respond when using larger displays. On my 5" based designs you have to go slow when using the on screen keyboard, for instance. With the 4.3" it is a lot better. If you have a lot of background processing it can be bogged down.
On the G400 there is more than enough response to type much faster due to the higher processing speed. Can’t wait to test this with the new Linux CPU. 
I also changed my ADC’s to SPI so that the I2C bus was only used for the touch and slow processing devices. When used with the ADC and processing them at 20 times per second, I saw a drop off on the touch response. Not much but it was there. I have also considered a second software I2C port to handle the touch.
2 Likes
@ Dave McLaughlin - ive been reading the documentation on the gpu of of the module, and it says that some sort of additional firmware is required. Have you encountered it as yet?