Sounds like you just put a new screen in it, possibly a bad connection/cable or even a bad screen.
Sent from my Moto G (4) using Tapatalk
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
- Thread starter sfhub
- Start date
Sent from my Moto G (4) using Tapatalk
If you are sure that the connection is 100% correct (the connection tape is not damaged), try to flash this Kernel (pure version)
https://forum.xda-developers.com/showthread.php?t=2449919
to do this you need to unlock the bootloader and flash TWRP recovery, then flash the kernel. you will need a mouse connected via OTG to choose options in the new recovery.
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
I just want to say thank you, thank you, thank you
To this man
boot ts 10 lock works very well with me
Im running official Lineage OS 18 Flox 10052021
I have spent and wasted lots of time and money trying to fix the touch screen.
Anyhow this has made my faulty touchscreen much more user friendly. no more ghost touches and glitches
To this man
boot ts 10 lock works very well with me
Im running official Lineage OS 18 Flox 10052021
I have spent and wasted lots of time and money trying to fix the touch screen.
Anyhow this has made my faulty touchscreen much more user friendly. no more ghost touches and glitches
Mod edit - translated by https://www.deepl.com/translator:
boot-ts file. The link in your post is Dead. Where can I find it?
**********************
файле boot-ts. Ссылка в вашем посте Мертва. Где я могу найти?
Attachments
Last edited by a moderator:
Mod edit - translated by https://www.deepl.com/translator:
Links are alive, screenshot error due to incomplete command, enter fastboot boot-ts10-lock.img
**********************
Ссылки живы, на скриншоте ошибка из-за неполного ввода команды, вводи fastboot boot boot-ts10-lock.img
Last edited by a moderator:
I was using TS10 on flo after screen replacements. Repartitioning moving to LineageOS 18 blew that away, but touchscreen OK until May 5 build:
lineage_flox-userdebug 11 RQ2A.210505.003 c83df746bd
I was just about to reinstall TSxx until I removed the case and plugged in the charger.
Now the touchscreen works. Go figure!?
With the case off, I notice the mainboard is quite warm. The infrared thermometer shows 41C at the top front and back. 29-31C at the bottom. It
lineage_flox-userdebug 11 RQ2A.210505.003 c83df746bd
I was just about to reinstall TSxx until I removed the case and plugged in the charger.
Now the touchscreen works. Go figure!?
With the case off, I notice the mainboard is quite warm. The infrared thermometer shows 41C at the top front and back. 29-31C at the bottom. It
Last edited:
Mod edit - translated by https://www.deepl.com/translator:
Thank you for your help, it was important to me)))
**********************
благодарю что помогли разобраться, это было важно для меня_)))
Last edited by a moderator:
- Apr 13, 2016
- 17,396
- 3
- 35,024
- 66
It looks like the ribbon and touchscreen cable connections lie at the root of touchscreen and rotation problems.
Note that the ribbon cable ends can be damaged.
When the mainboard gets corrupted signals, the behavior is corrupted.
When replacing a broken screen, it might help to also replace the ribbon cable. Removing the battery tray may make it easier to properly connect the creased end of the ribbon cable. Perhaps the USB board is the proper place for the creased end, but I just did it both ways on two N7s and they are both working fine.
Proper seating in the connectors is critical. I like the ribbon cables with pull tabs. You may want to use a magnifier to verify proper seating in the connectors.
Note that the ribbon cable ends can be damaged.
When the mainboard gets corrupted signals, the behavior is corrupted.
When replacing a broken screen, it might help to also replace the ribbon cable. Removing the battery tray may make it easier to properly connect the creased end of the ribbon cable. Perhaps the USB board is the proper place for the creased end, but I just did it both ways on two N7s and they are both working fine.
Proper seating in the connectors is critical. I like the ribbon cables with pull tabs. You may want to use a magnifier to verify proper seating in the connectors.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
331By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes? Suddenly you have dead spots, dead bands, ghost/phantom touches, stuck touches, broken drags, etc. Touchscreen works ok when held or plugged in, but is unusable on a table?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
- boot-ts10-lock.img
- boot-ts20-lock.img
- boot-ts30-lock.img
- boot-ts-unlock.img
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be using touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q, will work on LTE and custom ROMs also):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in this post.
- unpack the boot-ts.7z package using 7-zip
- you'll be left with a boot-ts directory with the aforementioned files
- connect your tablet by USB
- make sure USB debugging is enabled
Settings->About tablet [tap "Build number" 7 times]
Settings->Developer options [check "USB debugging"] - you can find adb/fastboot drivers HERE
- make sure USB debugging is enabled
- in a command prompt in the boot-ts directory type (commands in italics)
- adb reboot bootloader
- wait for the bootloader screen to come up
- alternatively use Power+VolDown to get to the bootloader/fastboot screen
- fastboot boot boot-ts10-lock.img
- this is how you try out package ts10
- the screen will hang for 18-24 seconds, this is NORMAL, do not touch
- this does NOT flash over your existing kernel
- wait until Android is COMPLETELY booted
- Note: if you are on Android 4.4 the stock 4.3 kernel will not get past the BouncingBalls
- wait 120 seconds for the boot to settle down
- press/hold the Power button 10-15 seconds until the tablet reboots
- proceed to next step
- adb reboot
- after booting to Android you MUST reboot at least once
- IGNORE any instability up to this point, it is expected
- if adb reboot does not work for some reason, use the power button to shutdown/reboot
- once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
- if there is instability, give it one more reboot back into Android before judging
- adb reboot bootloader
- if things are not working acceptably
- repeat step #3, with ts20, and ts30 if needed
- hopefully between ts10, ts20, and ts30, you will have found a package that works for you
- there is nothing else for you to do
- you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
- your touchscreen package is locked in place and won't change unless you want it to
- if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
- repeat step #3 using boot-ts-unlock.img
- upon first reboot you will have the touchscreen software from the installed ROM/kernel
Please post feedback with:
- the version of software you are running
- what was/is broken
- whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.9After many days of testing various patches, I've concluded on TS-16. Below are my test summary if it helps anyone.
Problems I faced with
- stucked touches, rather frequent
- ghost touches, very seldom. Only noticeable in very touch intensive games.
- missed touches, seems to happen a lot with typing.
- all the above happened regardless hand held or on a non conducting surface. Happens a lot more on a non conducting surface. A reboot usually fixes things for a while before it starts again.
TS10
- Works well, but has very seldom 5sec freezes that recoveries and goes wonky at bottom of screen after extended uses.
- Fixes stucked touches.
- No noticeable ghost touches or missed touches.
TS20
- Works and feels better both single n multi touch compared to TS10.
- BUT has unexplainable random system freezes that requires hard reset. Happens very occasionally and only in touch intensive programs.
- Fixes stucked touches, ghost and most missed touches.
TS25 and TS30
- Fixes stucked touches.
- Ghost touches becomes more frequent near bottom of screen.
- Touch feels a lil wonky too.
TS18
- Fixes stucked touches.
- Ghost touches and missed touches are unnoticeable.
- Multi touch in Google maps is less responsive.
- Random freezes also encountered as per TS20
TS14
- Fixes stucked touches
- Ghost touches and missed touches are unnoticeable.
- good responsiveness in google maps.
- typing feels a little inaccurate.
TS8 TS6 AND TS9
- all feels very sensitive.
- feels random wonkyness
- fixes stucked touches
- no noticeable Ghost touches and missed touches.
- typing seems overly sensitive and results in many errors.
- random wonkyness happens after extended use and short self recovered freezes.
TS16 - my favourite
- Fixes stucked touches
- no noticeable ghost touches or missed touches
- no random freezes experienced, not even the self recoverable freezes.
- good balance of sensitivity and accuracy.
- good multi touch responses in Google maps and Google earth.
- no problems in most instances when using on a flat surface.
Just a note to everyone. I have given at least 3-4 reboots after each update, and run them for at least 24 hours playing touch sensitive and intensive games like Turbo racing using multitouch to slide and more around.
Hope this helps. Thank you sfhub for filling the gaps where Google and Asus have not. Great patches for everyone to suit your usage patterns.
This entire message is typed using my nexus 7 2013 in dolphin browser.7Had enough. Smashed the N7 against a wall. Display broken. Worst piece of #%#& I bought in years. Never again.
Gesendet von meinem GT-I9505 mit Tapatalk6
So this guy goes to the doctor's office and says my head hurts everytime I hit the wall. The doctor says, then stop hitting the wall.
Couldn't you just slide it over and don't use the tablet on top of the keyboard?
Have you considered the MacBook Pro might be emitting interference? Stray currents and voltages? It doesn't take much to throw these capacitative touchscreens off.
On this thread, most people have it much worse than you making the tablet very hard to use. We are trying to get these units back into a state that is at least usable.
Your case, while an interesting science project really isn't something someone would feel any sense of urgency to help address.6
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
