Related
As the title says.. Whenever I use the hard key buttons the touchscreen stops responding + at times it randomly decides not to response. Kindly suggest..
Things I have done :
1.) Flashed new radio + ROM
2.) Removed screen protector.
3.) Did task 29 and then flashed a new rom.
Kindly help
Sounds like a hardware failure, which isn't uncommon for the touchscreen - search this forum for more examples.
Warranty or repair are your options.
Hey,
My phone continuously has a problem in which the W on the keyboard does not work. It presses the letters either side. Paired with this, now and then the screen appears to think i'm touching it, when I am not - the menus change, applications open, and the bottom buttons freeze - the screen becomes completely unresponsive.
Is there a solution to fixing this? I've tried switching roms and kernals?
noj123 said:
Hey,
My phone continuously has a problem in which the W on the keyboard does not work. It presses the letters either side. Paired with this, now and then the screen appears to think i'm touching it, when I am not - the menus change, applications open, and the bottom buttons freeze - the screen becomes completely unresponsive.
Is there a solution to fixing this? I've tried switching roms and kernals?
Click to expand...
Click to collapse
Tbh, I have no idea what to say. Do one thing, try flashing official firmware through odin and check if this error persists. If it doesn't then root the phone again and go to your favourite ROM. If it does, It could be a hardware problem of some sort. Best of luck
You can try Siyah kernel, I think it has some fixes for the touchscreen.
Sent from my Galaxy S2 GT i9100
boki9999 said:
You can try Siyah kernel, I think it has some fixes for the touchscreen.
Sent from my Galaxy S2 GT i9100
Click to expand...
Click to collapse
I have tried that kernal and the problem did continue. I haven't however flashed an official stock ROM since my first custom ROM. The problem is quite random which makes it impossible to replicate, I can just be using my phone for a few seconds and it will freeze up, then not do it for a week and it'll come back.
I am going to put on
"Official Stock ICS Firmwares
I9100XWLPT Download (Thanks To SamMobile!)
Base Firmware: I9100XWLPT (4.0.4)
Region: Europe"
And see if it'll sort out the issue. Currently my phone is essentially unusable due to the error - doesn't help I need this phone for tomorrow when I go on holiday.
Hey guys,
Been lurking on the site for a while, I've searched all morning for what i need but with no success.
Setup: Att sgh-i777 rooted etc. running JellyBam 5.1
Problem: Power button stopped working, cannot use recovery to backup/flash new software.
Plenty of threads on the button issue, that's not the main question (suggestions welcome though) I just really want to backup before I send it off for repair.
Seems my best course of action is to get a kernel with touch based recovery. I tried downloading mobile Odin to flash a new kernel but it's telling me my phone isn't supported for some reason? I ran the dump file Odin suggested but not sure what to do with that info now. Next best option appears to be to get a .tar of the siyah kernel and flash it with Odin via PC. I just can't find a .tar for that kernel anywhere and I don't have enough posts to ask in the siyah thread.
So, can anyone give me a hand- either with trouble shooting mobile odin, or tracking down a .TAR of the siyah kernel or...any other suggestions?
Edit: Just found this- http://forum.xda-developers.com/showthread.php?t=1644240
I realize this is in the 9100 forum but looks like it simply converts a zip to an odin flashable tar which is what i'm looking for. Anyone have any experience with it?
Thanks in advance for any insight!
You want to do a nandroid backup? Yes just flash the siyah kernel in the development forum with mobile Odin. It does work with our phones.
Phalanx7621 said:
You want to do a nandroid backup? Yes just flash the siyah kernel in the development forum with mobile Odin. It does work with our phones.
Click to expand...
Click to collapse
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
flet2 said:
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
Click to expand...
Click to collapse
It possibly can be ROM related (but I am not certain). User AJ's Siyah kernel 7.6.8, it's works well with all the ROMs.
BeenAndroidized said:
It possibly can be ROM related (but I am not certain). User AJ's Siyah kernel 7.6.8, it's works well with all the ROMs.
Click to expand...
Click to collapse
Yup, running 7.6.7 now and enjoying it.. My power button is currently working again but i turned on 'swipe to wake' in Stweaks so when it fails again, at least i'll still have a working phone. the volume wake from AOKP settings doesn't work when the phone is in deep sleep so pretty useless. As long as i stay on Siyah kernel i guess i'll be able to limp along until i get the button fixed.
The Odin thing is still strange though, will have to try another ROM and see if it recognizes my phone then. Tried Jellybam 4.1 but kept getting reboots even with full wipe- tried flashing it twice. Maybe i got a bad download, i'll try again tonight.
flet2 said:
Yup, running 7.6.7 now and enjoying it.. My power button is currently working again but i turned on 'swipe to wake' in Stweaks so when it fails again, at least i'll still have a working phone. the volume wake from AOKP settings doesn't work when the phone is in deep sleep so pretty useless. As long as i stay on Siyah kernel i guess i'll be able to limp along until i get the button fixed.
The Odin thing is still strange though, will have to try another ROM and see if it recognizes my phone then. Tried Jellybam 4.1 but kept getting reboots even with full wipe- tried flashing it twice. Maybe i got a bad download, i'll try again tonight.
Click to expand...
Click to collapse
Try 7.6.8, I'm using 7.6.8-S and swipe works perfectly fine on my end.
BeenAndroidized said:
Try 7.6.8, I'm using 7.6.8-S and swipe works perfectly fine on my end.
Click to expand...
Click to collapse
Oh yea the swipe to unlock for siyah works great. I was referring to JellyBam's AOKP settings which offers a volume to wake. Volume wake works when on charger, but won't wake it from deep sleep. Siyah's Swipe wake does both :good:
I would still love to have an odin flashable .tar of siyah though- If anyone has any insight on how to get that (or make it from the .zip) that would be awesome. I used the tool from the thread linked in the OP and it did turn the kernal zip into a .tar but i don't dare flash it to test...
flet2 said:
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
Click to expand...
Click to collapse
Read somewhere that jellybam 5.1.0 places the wrong phone info in the rom. It show up as i777 instead of sgh-i777 and this might be causing Mobile odin to fail on the compatibility test.
To turn your volume up button into a power button edit the /system/usr/keylayout/gpio-keys.kl file to read:
key 115 POWER WAKE
key 114 VOLUME_DOWNWAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
key 115 is the volume up button. This only works in the fully booted os. Doesn't work in recovery.
Sent from my Apple IIe
Quicksilver13 said:
Read somewhere that jellybam 5.1.0 places the wrong phone info in the rom. It show up as i777 instead of sgh-i777 and this might be causing Mobile odin to fail on the compatibility test.
Click to expand...
Click to collapse
Yup that was exactly it. I notice it when i went back to Jellybam 4.1 and saw the full device name in the 'about'. Hopefully 5.2 drops soon with all the necessary fixes!
billyjed said:
To turn your volume up button into a power button edit the /system/usr/keylayout/gpio-keys.kl file to read:
key 115 POWER WAKE
key 114 VOLUME_DOWNWAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
key 115 is the volume up button. This only works in the fully booted os. Doesn't work in recovery.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for this info. Is there a thread or tutorial somewhere that will explain how to access and edit this file? I assume it's not as simple as just navigating to it and making the changes?
Also, how do i get volume to go up if i turn it into a power button? wouldn't that make my phone lock every time i tried to turn up the volume then?
flet2 said:
Yup that was exactly it. I notice it when i went back to Jellybam 4.1 and saw the full device name in the 'about'. Hopefully 5.2 drops soon with all the necessary fixes!
Thanks for this info. Is there a thread or tutorial somewhere that will explain how to access and edit this file? I assume it's not as simple as just navigating to it and making the changes?
Also, how do i get volume to go up if i turn it into a power button? wouldn't that make my phone lock every time i tried to turn up the volume then?
Click to expand...
Click to collapse
It actually is just as simple as finding the file, mounting the directory as r/w and then editing the file. As far as turning up volume, you would have to turn down volume and then use the on screen volume panel to adjust.
Sent from my Apple IIe
Great thanks. So to mount the directory it appears i need to use ADB, or could i use an app such as Root explorer or something like this? https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en
Can i access the file right from my phone to make the changes once i have the directory mounted correctly?
flet2 said:
Great thanks. So to mount the directory it appears i need to use ADB, or could i use an app such as Root explorer or something like this? https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en
Can i access the file right from my phone to make the changes once i have the directory mounted correctly?
Click to expand...
Click to collapse
I use root explorer on the phone. If you use a rom that has support, you can add a line into your addon.d files to keep from having to manually change it everytime you update your firmware.
Sent from my Apple IIe
Thx for the info, i'll have to test this out. I'll nandroid and back up the original file too just incase!
Let me know how it works out for you.
Sent from my Apple IIe
Hi,
My wife's power button went out on her i777. Backed up the file and changed key 115 to power wake. Rebooted. This made volume up and down both stop working. Changed it back, they both work. Any ideas?
I have it running AOKP with AJK kernel.
Hey guys,
I upgraded to the irish official 4.3 (I9300XXUGMJ9_I9300VFGGMJ5_I9300BUUGMJ3_HOME) from cm 10.2.
I now have a battery drain, it takes about 8 hours from 100% to 0% with an hour screen time. Also sometimes after turning off the screen I can't get the phone to start again without taking out the battery.
I did a full wipe after installing 4.3 and I'm considering another factory reset/wipe, but wanted to see if there is another solution before doing this.
Thanks for any help.
Read that roms thread multiple posts on the subject no need for a new thread .
JJEgan said:
Read that roms thread multiple posts on the subject no need for a new thread .
Click to expand...
Click to collapse
True true. I read a few extra pages back and it seems a few people are having issues.
I remember having this issue a few months back, go into your settings and go to battery. Is "Android OS" at the top or very close? If it is then the reason was (in my case) the device couldn't go into deep sleep mode which should happen when you lock your device, this means that instead of nearly shutting down and only having the data connection on (maybe wifi aswell), the device was running the same as before you hit the power button, the only difference is that the screen is that the screen is off. There are different reasons for this happening but for my device it was a kernel issue, this means that these steps may not work for you, because like i said, this issue is different every time.
All i had to do to fix this issue was flash a new kernel, i chose the googy max kernel 1.7.5 for CWM, which is a continued development of the siyah kernel, after the developer abandoned it.
Yoiu just have to flash it the same way you did Cyanogenmod, go into CWM (or another custom recovery) and flash it to the device.
This concerns kernel devs and people with touchscreen problems.
As I saw android 4.4 updates didn't fix the touchscreen for some. In addition it made things worse, like in my case.
So I tried to force firmware updating the touchscreen module and try many different firmwares.
To ease that process I modified the already existing code of the drivers (ektf3k.c) to enable firmware update by demand and using a filepath.
In the package below you will find the modified driver source file for custom kernel developing, all firmware updates until now and a help file for how to flash them.
All fw were modified to a version number of 99, to lock them in place and not let future auto updates (unlock fw included).
Kernel driver source + Firmware files
EDIT: Added patch, check below
EDIT2: Corrected the typo in patch. Thanks @Tk-Glitch
After creating the custom kernel, you can use terminal or adb or a text editor to echo or edit /sys/devices/i2c-3/3-0010/update_fw and write the fw filepath. You can also check fw version by checking /sys/devices/i2c-3/3-0010/vendor (the last numbers are your fw version).
Check readme for more
To all kernel devs:
The modified drivers do not break anything. They just create a special sysfs file. The code is activated only by writing a path in that sysfs file.
To all others with touchscreen problems:
This needs a custom kernel with this modified driver. Otherwise you can't use the firmware files
Kernels with touchscreen force update patch:
Glitch
SaberMod franco.Kernel
X-Flo
If you incorporated the patch into your kernel please inform me to update the list.
Changelog of touchscreen firmwares:
Code:
A011:
A011 is the lastest touch firmware and used for factory image.
firmware update history:
A009:
Update boot-code Ver: 60.47 (Do not turn off WDT in IAP process).
Add Self Check Mechanism to enter suspend mode.
Modification Algorithm, and Digital Parameters for ER Module.
a. Improve "double fat finger (22 phi copper)" performance.
b. Improve "fast drawing straight line" performance.
c. Improve "multi-finger in co-axis (8 phi copper)" performance.
d. Improve "under table lamp" performance.
A010:
Modify Calibration Mechanism.
A011:
Modify Open/Short Calibration Mechanism for ESD problem.
Improve Stylus Performance
=================================================================
A012:
1.Fix the Sensitivity Problem That Suspend and Wake up When Charging.
2.Modification for Algorithm, and Digital Parameters for ER Module.
a.Improve "double fat finger (22 phi copper)" performance when charging.
=================================================================
A021 (A015):
Fix:
8717455: Holding touch panel edge by one finger,the touch action will be affected.
8768005: Holding Flo along the left edge of the device reveals false touch problems.
8840158: Pinch zoom in and out on chrome and maps doesnt seem as accurate / responsive as on nakasi.
8798827: Touch can not be correct clicked.
customer report: pin unlock will lose touch report.
Modification for AC De-noise Mechanism.
=================================================================
A025:
Based on A023 and remove the grip information.
1.[Issue 8840158] [FLO] pinch zoom doesnt seem as responsive / reliable as on nakasi.
2.[Issue 8858019] [FLO] Poor touch resolution.
Need calibration to fix these two issue with ER1/ER2 device:
3.[Issue 9052815] [FLO] Dead "Bands" on the touch screen.
4.[Issue 8930391] Spurious touchscreen taps.
=================================================================
A028:
Improve hovering like Nakasi
=================================================================
A029:
Need calibration for below Issue:
[Issue 9261425] New touch firmware is needed to apply the new parameters.
=================================================================
A031:
Fix following issues:
1.Latency on resume
2.Edge swipes lost (notification panel)
3.[Issue 9284036][FLO]ABS_MT_TOUCH_MAJOR values change
base on number of pointers down
=================================================================
A032:
1.firmware to A032.
2.modify driver to update power source when use slim port to hdmi.
A032 fix issue:
9471817:Hover touches.
9366206:Device show multiple-ghost touch after connect HDMI and tilt device to 40~65 degree.
9471956:Unclean lift offs.
9471962:Edge swipes causing hooks or missing touch points.
Noise problem.
Add ESD Protection Mechanism.
=================================================================
A033:
Fix issue:
1.Seeing lost touches.
2.Magic disappearing square.
3.Need to clean up small pointer dancing.
4.Pointer splitting.
5.Jumps between two large touches.
6.9521124:Poor performace in handwritten input method.
Bug: 9472154
Bug: 9471828
Bug: 9521124
Bug: 9471817
=================================================================
A034:
improvement:
9323363:Scrolling not smooth.
=================================================================
A036:
Fix issue:
962875:Need a new touch firmware to pass ESD test.
=================================================================
A038:
Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games
2.[Issue 9323363] [FLO/DEB] [Touch] Scrolling not smooth
3.[Issue 9471817] [FLO/DEB] [Touch] Hover touches
=================================================================
A040:
Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games.
2.Broken line.
3.Two Fingers Tapping Easy Connectivity.
4.co-axis problem with two finger.
=================================================================
A042:
Fix/Improve issue:
1.ghost touch probelm that caused by lcm slef-noise.
2.broken line in particular area.
=================================================================
A043:
Bug: 10388772
Bug: 10391124
Bug: 10541253
=================================================================
A044:
Fix issue:
1. Improve stability of two finger co-axis.
2. Ghost point problem of two fingers.
I've never had a touch screen problem
I have had touch issues. Not so much with 4.4.4
Sent from my Nexus 7 2013 using Tapatalk
CTCaer said:
This concerns kernel devs and people with touchscreen problems.
As I saw android 4.4 updates didn't fix the touchscreen for some. In addition it made things worse, like in my case.
So I tried to force firmware updating the touchscreen module and try many different firmwares.
To ease that process I modified the already existing code of the drivers (ektf3k.c) to enable firmware update by demand and using a filepath.
In the package below you will find the modified driver source file for custom kernel developing, all firmware updates until now and a help file for how to flash them.
All fw were modified to a version number of 99, to lock them in place and not let future auto updates (unlock fw included).
Kernel driver source + Firmware files
EDIT: Added patch, check below
After creating the custom kernel, you can use terminal or adb or a text editor to echo or edit /sys/devices/i2c-3/3-0010/update_fw and write the fw filepath. You can also check fw version by checking /sys/devices/i2c-3/3-0010/vendor (the last numbers are your fw version).
Check readme for more
To all kernel devs:
The modified drivers do not break anything. They just create a special sysfs file. The code is activated only by writing a path in that sysfs file.
To all others with touchscreen problems:
This needs a custom kernel with this modified driver. Otherwise you can't use the firmware files
Changelog of touchscreen firmwares:
Code:
A011:
A011 is the lastest touch firmware and used for factory image.
firmware update history:
A009:
Update boot-code Ver: 60.47 (Do not turn off WDT in IAP process).
Add Self Check Mechanism to enter suspend mode.
Modification Algorithm, and Digital Parameters for ER Module.
a. Improve "double fat finger (22 phi copper)" performance.
b. Improve "fast drawing straight line" performance.
c. Improve "multi-finger in co-axis (8 phi copper)" performance.
d. Improve "under table lamp" performance.
A010:
Modify Calibration Mechanism.
A011:
Modify Open/Short Calibration Mechanism for ESD problem.
Improve Stylus Performance
=================================================================
A012:
1.Fix the Sensitivity Problem That Suspend and Wake up When Charging.
2.Modification for Algorithm, and Digital Parameters for ER Module.
a.Improve "double fat finger (22 phi copper)" performance when charging.
=================================================================
A021 (A015):
Fix:
8717455: Holding touch panel edge by one finger,the touch action will be affected.
8768005: Holding Flo along the left edge of the device reveals false touch problems.
8840158: Pinch zoom in and out on chrome and maps doesnt seem as accurate / responsive as on nakasi.
8798827: Touch can not be correct clicked.
customer report: pin unlock will lose touch report.
Modification for AC De-noise Mechanism.
=================================================================
A025:
Based on A023 and remove the grip information.
1.[Issue 8840158] [FLO] pinch zoom doesnt seem as responsive / reliable as on nakasi.
2.[Issue 8858019] [FLO] Poor touch resolution.
Need calibration to fix these two issue with ER1/ER2 device:
3.[Issue 9052815] [FLO] Dead "Bands" on the touch screen.
4.[Issue 8930391] Spurious touchscreen taps.
=================================================================
A028:
Improve hovering like Nakasi
=================================================================
A029:
Need calibration for below Issue:
[Issue 9261425] New touch firmware is needed to apply the new parameters.
=================================================================
A031:
Fix following issues:
1.Latency on resume
2.Edge swipes lost (notification panel)
3.[Issue 9284036][FLO]ABS_MT_TOUCH_MAJOR values change
base on number of pointers down
=================================================================
A032:
1.firmware to A032.
2.modify driver to update power source when use slim port to hdmi.
A032 fix issue:
9471817:Hover touches.
9366206:Device show multiple-ghost touch after connect HDMI and tilt device to 40~65 degree.
9471956:Unclean lift offs.
9471962:Edge swipes causing hooks or missing touch points.
Noise problem.
Add ESD Protection Mechanism.
=================================================================
A033:
Fix issue:
1.Seeing lost touches.
2.Magic disappearing square.
3.Need to clean up small pointer dancing.
4.Pointer splitting.
5.Jumps between two large touches.
6.9521124:Poor performace in handwritten input method.
Bug: 9472154
Bug: 9471828
Bug: 9521124
Bug: 9471817
=================================================================
A034:
improvement:
9323363:Scrolling not smooth.
=================================================================
A036:
Fix issue:
962875:Need a new touch firmware to pass ESD test.
=================================================================
A038:
Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games
2.[Issue 9323363] [FLO/DEB] [Touch] Scrolling not smooth
3.[Issue 9471817] [FLO/DEB] [Touch] Hover touches
=================================================================
A040:
Fix/Improve issue:
1.[Issue 9692415] Touch screen on flo is broken for games.
2.Broken line.
3.Two Fingers Tapping Easy Connectivity.
4.co-axis problem with two finger.
=================================================================
A042:
Fix/Improve issue:
1.ghost touch probelm that caused by lcm slef-noise.
2.broken line in particular area.
=================================================================
A043:
Bug: 10388772
Bug: 10391124
Bug: 10541253
=================================================================
A044:
Fix issue:
1. Improve stability of two finger co-axis.
2. Ghost point problem of two fingers.
Click to expand...
Click to collapse
Been looking for something like this that embeds all the firmware variants in one package. Guess it's not usable unless integrated in some custom kernel... Will have to wait for aroma installer then. But thanks.
Well many have problems and were forced to flash custom kernels with different firmwares.
This can ease up a lot the process and help many people that are using custom kernels to test different fw.
For example many fixed their issues with A011 (aka ts10). Because like in my case, the problem comes from the LCD's electromagnetic interference on ELANtech's touch panel(tested with Nexus 7 Nexus 7 II Tester).
Well it's up to kernel dev's to incorporate the driver mod if they want.
I may make a stock based custom kernel, touch fw tester edition, when I get back home and refix my ubuntu vm.
So 1 flash, try firmwares, find the personal best, reflash previous kernel.
Hello, thanks for the patch, i'm using Glitch Kernel which implemented your patch and i'm going to try and fix my touchscreen but i want to know which version of the driver is the latest, is it the A011 or the A044?
And another question, i've just tested A011 and A044 but at vendor both show ELAN_KTF3K_xa064, are they both supposed to show the same version?
Trevomader said:
Hello, thanks for the patch, i'm using Glitch Kernel which implemented your patch and i'm going to try and fix my touchscreen but i want to know which version of the driver is the latest, is it the A011 or the A044?
And another question, i've just tested A011 and A044 but at vendor both show ELAN_KTF3K_xa064, are they both supposed to show the same version?
Click to expand...
Click to collapse
Yeah both of them show the same version to avoid updating to new one.
I may release an archive with incremental (bigger than a044) sometime.
The latest is A044 since months.
Also thank you for testing this mod.
Good luck mitigating the problem.
EDIT: Checked @Tk-Glitch kernel commits and corrected the typo to the above patch. Thanks
For the longest time I had crazy touch problems especially when I set the device down on the bed, etc, not unlike many others..but a week ago I pulled my screen protector off and all problems have completely vanished, put another one on, problems return immediately, can anyone explain this? And also is there a screen protector that I can use i.e, tempered glass, for anyone that found the same problem
trident76 said:
For the longest time I had crazy touch problems especially when I set the device down on the bed, etc, not unlike many others..but a week ago I pulled my screen protector off and all problems have completely vanished, put another one on, problems return immediately, can anyone explain this? And also is there a screen protector that I can use i.e, tempered glass, for anyone that found the same problem
Click to expand...
Click to collapse
Some have reported the same problem with screen protectors. I had similar issue with 2012 Nexus 7 when the screen got dirty with finger prints. I now use Nova screen. Lag almost unnoticeable. Matter of fact, it's mostly grounding issue. Too bad there still isn't a way to flash the OP batch, though, according to other threads, the multi-touch fix isn't for that. YAMTT records no problem, but if I leave it flat on a table, some areas don't register touches at all. I've used EMI tape as much as I can see and yet, no improvements. I guess it's between the LCD and the touchscreen. That being the case, no cure.
Hi @CTCaer,
I have touchscreen problems on my N7 Flo :crying:. Can you say me how I can test this patch? Or which kernel I must flash? It's there one, which have your patch already intergrated?
Thanks! :victory:
raXoN91 said:
....Can you say me how I can test this patch? Or which kernel I must flash? It's there one, which have your patch already intergrated? ....
Click to expand...
Click to collapse
Hey, check 1st post.
I added a list that I'll try to maintain
CTCaer said:
Yeah both of them show the same version to avoid updating to new one.
I may release an archive with incremental (bigger than a044) sometime.
The latest is A044 since months.
Also thank you for testing this mod.
Good luck mitigating the problem.
EDIT: Checked @Tk-Glitch kernel commits and corrected the typo to the above patch. Thanks
Click to expand...
Click to collapse
Do you know if there was a change from android 4.4 to 4.4.2 in the driver? From memory 4.4 seemed to be perfect and around 4.4.2 I started getting problems again (ghost touches)
CTCaer said:
Hey, check 1st post.
I added a list that I'll try to maintain
Click to expand...
Click to collapse
Hey, I fashed the Glitch kernel r151 and the issue is not fully fixed. It's Vetter! But ff the tablet get hot, the issue come again. Is there a special Version with the patch? Thanks :victory:
godutch said:
Do you know if there was a change from android 4.4 to 4.4.2 in the driver? ..
Click to expand...
Click to collapse
No it's A044. But when I updated 4.4.3->4.4.4, I checked logs and the touchscreen driver wrote something with calibration (can't remember exactly).
raXoN91 said:
Hey, I fashed the Glitch kernel r151 and the issue is not fully fixed. It's Vetter! But ff the tablet get hot, the issue come again. Is there a special Version with the patch? Thanks :victory:
Click to expand...
Click to collapse
The firmwares can't completely fix the problem, only can make the situation better. The device getting hot means that it uses a lot of power and thus more EMI for the touchscreen panel.
You have to test different fw because almost every fw has different internal calibration methods.
Also I learned that the correct way to use the forced calibration (as I mentioned in the other touchscreen problems thread, echo "FF" > /proc/ektf_dbg), is to put the device on an insulated surface, away from power sources, chargers and do it by using terminal emulator and not adb with wifi or cable. And also in flight mode.
CTCaer said:
No it's A044. But when I updated 4.4.3->4.4.4, I checked logs and the touchscreen driver wrote something with calibration (can't remember exactly).
The firmwares can't completely fix the problem, only can make the situation better. The device getting hot means that it uses a lot of power and thus more EMI for the touchscreen panel.
You have to test different fw because almost every fw has different internal calibration methods.
Also I learned that the correct way to use the forced calibration (as I mentioned in the other touchscreen problems thread, echo "FF" > /proc/ektf_dbg), is to put the device on an insulated surface, away from power sources, chargers and do it by using terminal emulator and not adb with wifi or cable. And also in flight mode.
Click to expand...
Click to collapse
I've noticed that Franco's kernel with embedded firmware comes in 2 versions: AOSP and CM. Should I switch between the two, would it be necessary to unlock the patch and reflash it again with the version that corresponds with the new rom? Thank you.
graphdarnell said:
I've noticed that Franco's kernel with embedded firmware comes in 2 versions: AOSP and CM. Should I switch between the two, would it be necessary to unlock the patch and reflash it again with the version that corresponds with the new rom? Thank you.
Click to expand...
Click to collapse
AOSP and CM are only the versions that are supposed to match with your rom. AOSP are the majority of the roms you'll probably use. (Stock, PA) CM are roms mostly derived from CM (basically CM, PAC)
In that case you only need to flash the rom if not already done. Then you need to flash the corresponding kernel version and you can use the said patch.
Envoyé de mon Nexus 7 en utilisant Tapatalk
zaclimon said:
AOSP and CM are only the versions that are supposed to match with your rom. AOSP are the majority of the roms you'll probably use. (Stock, PA) CM are roms mostly derived from CM (basically CM, PAC)
In that case you only need to flash the rom if not already done. Then you need to flash the corresponding kernel version and you can use the said patch.
Envoyé de mon Nexus 7 en utilisant Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Guess I wasn't very clear. I'm now on CM-derived rom. So I flashed CM-based patched kernel. But if I decide to switch to an AOSP-based rom, do I need to unlock the CM firmware and flash the AOSP firmware instead? Or is it the case that once you flash it, it would stick until you unlock again, no matter what rom you install in between?
It locks it. Doesn't matter the kernel. It will only update it if the touchscreen goes into recovery mode.
To unlock it, use A044-unlock.b. This is untouched, so it will show _xA044 in the vendor sysfs and not _xA064.
Hello again, yesterday i've tried to "unlock" the firmware, but even after applying A044-unlock.b multiple times it's still showing version 100 (x64) on vendor.
I'm still on glitch kernel, so i don't know if the patch is working correctly on this kernel.
Try the attached file. It's stock A011.
If it succeeds and you reboot the driver should then flash the kernel's stock which is A044 (it should show _xa044).