I do however need some very basic questions answered, one of which is covered by Cheuk below. I need some detailed information that will allow a decision to be made on what the order of precedence is on the firmware, the strengths and weakness of each and any specific impact.
1. As Cheuk’s email below, Inspired investigated the issue and found by trial and error that the settings we proposed provided a risk reduction of the major touch issue. We do however need to have official response as to what these changes actually do, why they affect the touch as they do and if they meet GT requirements in regards to touch settings that they would suggest.
2. The Multi Touch and the single touch both produce an error when checking with the tuning tool – see Firmware Comparisons – 15 Oct Tuning Tool. We do not see this error when using 6471-C-04.hex
a. Why are we getting these errors, is there something to be concerned about?
3. For both the single touch and multi touch provided today, what production version was used as the baseline?
a. 1st Production version
b. 2nd Production version but XY Resolution changed.
c. Brand new Production version.
4. When the GT Engineer visit Trio and look at the issue, then produced the 2 firmware’s, exactly what did they find, why were the changes made, what was changed and why? What level of touch removal for mobiles do they provide.
5. Does the original production firmware use mouse mode or not?
a. Different firmware shows different settings using the tuning tool, why?
b. How do we check if an original panel is in mouse mode or not?
6. We need a detailed explanation on firmware naming convention, core config, PID and VID.