[Galaxy S 4 Q&A, Help & Troubleshooting] kosmodisk:
Dear [MENTION=2769354]vanito[/MENTION],

1. As [MENTION=3232118]mc2mc2[/MENTION] mentioned (thx), this post was supposed to be some kind wrap up of this thread as it was really chaotic and the people are asking the same things all over and over.

2. Yes it's clear that there are two version of this chip, because that's what we've found during our investigation (and also it was buried inside this thread...)

3. Congratz, if you've tried to switch the chip 236A for 0065 1 year ago, but it's not very helpful when you keep this information for yourself - I've tried that and it was completely FREE sollution for me, so I just wanted to confirm that it works (I wasn't 100% sure that it'll work, as there could have been more differences on the boards - but I took the risk)

4. Solution - ok, I agree that I might have written something like "Current Solutions..." - but does it really matter?

Now try to think first, when choosing between HW and SW solution

You cannot be further from truth by writing: "Also you change HW side, Problem in SW remain and can turn back, also if with one Stock Rom is working, at 1/2 or 3 change of Stock Rom."

- Even if somebody finds the way how to force touchkey FW flash (which I believe isn't that hard for rom cooks as the kernel source code is pretty straight forward), it will fix the problem only temporarily => each newer stock ROM would cause the malfunction of the keys to return and fix will need to be applied after each flash, so in fact the SW solution will be temporary

+ I've written to several kernel authors if they could create modded kernel and got NO answer (It's hard for me to get some time to go through all this cooking stuff and learning it by myself...)

+ We would need to reverse engineer the FW and flash modified version to resolve this issue (f.e. change version id in FW 0x10 to 0x12 to trick the check)

- On the other hand HW fix can be completely free if you have friend who can resolder this as the most of the people have access to their broken OEM screen with original IC (0065) => moreover this fix is permanent!

So the summary shows up the best we have right know (and yes HW solution is currently the only real fix for this issue), if you have something better, feel free to share...

regards!

---------- Post added at 02:28 PM ---------- Previous post was at 01:50 PM ----------

What I was trying to achieve at first when trying to solve this by SW:

- I've checked logcat bootup log and found references to cypress-touchkey module.

- I've located the module in accessible kernels and studied the source code

- I've found out, there there are methods called every time on reboot, these methods check touchkey IC's FW and if it is lower than expected the flash is performed (this is the place where removing the check could enable us to at least force the downgrade of the FW and it should be possible by simple commenting out of several if related lines)

Check for example this source code

=> I just don't have all the necessary tools and the setup of linux workstation to compile the kernel after changes. I've tried the compilation several times but wasn't sure that I've done it the right way

- The approach used in the thread you've mentioned is better for sure, but it requires more changes in the file (however if we will be able to update the driver source code, they could help us with the rest)