Screenproblems and a Customwarequestion... - Vega General

I have a Viewsonic Viewpad 10s and some problems with the screen, I flashed at first the version Vegacomb 9n + Update 3. At the beginning it was wonderful but then the screen does not work properly. Even after a reboot did not care much. I went to ClockworkmodRecovery and flashes Honey Ice, it was back to normal. Some time later came the same problem, can someone tell me what it is?
The other question is, what ROM is to recommend the best? The tab is a Christmas present, I do not want to have again after 2 days because it is not reasonable ...
I am in a German forum, but there are not really someone who has the problem with the screen ...

Megamanwwh said:
I have a Viewsonic Viewpad 10s and some problems with the screen, I flashed at first the version Vegacomb 9n + Update 3. At the beginning it was wonderful but then the screen does not work properly. Even after a reboot did not care much. I went to ClockworkmodRecovery and flashes Honey Ice, it was back to normal. Some time later came the same problem, can someone tell me what it is?
The other question is, what ROM is to recommend the best? The tab is a Christmas present, I do not want to have again after 2 days because it is not reasonable ...
I am in a German forum, but there are not really someone who has the problem with the screen ...
Click to expand...
Click to collapse
I had the same problem with my Viewpad 10s with Vegacomb, HoneyIce and newer roms. One of the original issues was using it while it was plugged into the charger the screen became either unresponsive, or would randomly apply keystrokes that were not touched. Two people posted solutions, heating the outside of the tab with a hair dryer, and putting more pressure on the tab (squeezing the case) as you were touching the screen. I did find the extra pressure did help, but it was crazy trying to get the pressure just right. also noticed that screen worked differently in portrait and landscape mode. I often had to use portrait mode to slide the unlock across, while landscape would not allow the tab to unlock.
I decided to "downgrade" the rom to stock, it worked, then to modified stock, it worked but had some touchscreen inconsistencies, then to Corvus 5 rom, which I read somewhere solved other peeps touchscreen problems. Once I got Corvus 5 up and unlocked, I used his screen recalibration tool in apps and everything works perfect. I've been up and running for a month with no touchscreen problems. I even backed up Corvus 5, and tried Vegacomb and HoneyIce again. They worked for a couple of days, and then tab went back to touchscreen issues. I'm thinking it's a kernel sensitivity issue, but I'm know expert, and it's not happening on enough tabs for devs to take as a serious issue.
Hope this helps!!

you are one of the lucky ones man..i tried Corvus 5, true the method you described and still have the issues, well..actually i tried every single Rom and no luck.
I know it's mostly a hardware problem, the only differences in Rom's is the heating they produce, some more, some less..so depending on how bad your case is, you might find a balance and make it work for some time..or no time..
By the way, anyone knows if it's possible to disable the touchscreen inputs, from terminal, adb commands or maybe some app?

Related

My touchscreen no longer works

Starting today, my touchscreen just doesn't register anything. It's not cracked or damaged at all. It just stopped responding. I can still use my dpad but my phone is extremely limited at this point.
I'm currently running Myn's Warm Eclair: http://forum.xda-developers.com/showthread.php?t=691174
I really don't want to format my phone to figure out if it's a software problem but does anyone know if this is just a problem with this android build or with android on our phone in general?
thehelios said:
Starting today, my touchscreen just doesn't register anything. It's not cracked or damaged at all. It just stopped responding. I can still use my dpad but my phone is extremely limited at this point.
I'm currently running Myn's Warm Eclair: http://forum.xda-developers.com/showthread.php?t=691174
I really don't want to format my phone to figure out if it's a software problem but does anyone know if this is just a problem with this android build or with android on our phone in general?
Click to expand...
Click to collapse
It has been a problem for me with some builds. I suggest you to make a backup with some app like Titanium Backup and reinstall Android. Try with different kernels if you still have the problem. Don't worry for the moment!
I have had this problem a few times. I still can't quite figure out exactly what makes it happen but it seems to be something to do with sleep. My solution is to restart and go into NAND then do a backup apps and then quit. something gets woken up in the screen and it starts to work again. No idea why, it just does. Good luck.
So I guess my touchscreen is just dead. I reinstalled android, reflashed my phone for the froyo rom, and I even flashed a windows rom onto my phone but nothing. I even opened my phone to see if it was connected properly to the mobo but all seems right.
On the windows rom, when it does the screen calibration, I can mash the crap out of my screen and I guess it picks up some sort of signal every now and then because the crosshair moved.
If anyone knows anything about this, please reply. I don't really want this to be the end of my vogue. It's been a good 3 years so far!
http://cgi.ebay.com/Touch-Screen-Di...749473?pt=PDA_Accessories&hash=item439b537fa1
You may just need a new Digitizer.
Can get them pretty cheap on e-bay - just have to wait since coming international mail.
I am having similar problems. Usually when the phone goes to sleep and I wake it up the touch screen is unresponsive. Only way to get touch to respond is to reboot.
I have tried it on my vogue on both the fresh froyo and experimental fat free froyo using both the 10-9 and 9-29 kernel on nand. I have also used nbh editor to change the panel types (vogue uses auto detect so I changed it to Polaris) and still the same problem. I thought perhaps there was a problem with a program but I have no programs installed right now and the problem still persists.
Does anyone have any suggestions? My phone was working fine up to a few weeks ago and I would hate to be forced to use windows again. I have reinstalled windows and it works fine there so I don't think it is hardware related. It seems something happens when it goes to sleep.
Well there might be a driver issue. Try going back to the stock rom for your device and see if the touchscreen works, if it doesn't work, then it's probably broken. Try opening the vogue and disconnecting and reconnecting and then turning your device back on and test it again. if it still doesn't work, then yea you will have to get a new digitizer.
You can also try using other releases/roms with different kernels.
good luck!! and may your vogue live on!!
Thanks, I've installed a windows rom and the touchscreen has no issue there so it leads me to believe it is not the digitizer, especially because it seems to break when it goes to sleep.
I will try even older kernels and perhaps a donut build to see if the problem still exists.
Try to figure out when things broke for you by trying the kernels that have been released over the past month. Maybe we can isolate the change that broke things for you. Maybe not, but it's worth a try.
n2rjt said:
Try to figure out when things broke for you by trying the kernels that have been released over the past month. Maybe we can isolate the change that broke things for you. Maybe not, but it's worth a try.
Click to expand...
Click to collapse
Hi! I had this problem, that was the reason why I put back WM. I experienced it using .32. I think it was from 1-Oct-2010 approximately when it started to fail.
IT'S A CONSPIRACY!!!! Last week my screen broke as well. I was running "not so super froyo" and it would work for a second then just be completely unresponsive... needless to say I now have a droid x *fap**fap*

[Q] NAND Screen stays off after phone call

Hi All
Was using SD versions of Android in my HD2 which worked quite well .....decided to make the jump to NAND recently but I'm having a problem with phone calls.
When I make a call out, everything works fine, but when I hang up on the call, the hard buttons on the bottom of the phone all light up but the screen doesn't turn back on.... Only way to get the screen back on is to plug in the USB cable or power adapter or pull the battery and do a reboot!
Have tried a couple of different builds from different chefs and a couple of Radios just in case.
At the moment I've got the following on it:
Radio is 2.12.50.02_2
Android version is 2.2.1
Build is DL DesireZ v3.4 Final (but this problem also happens with CleanDROID V1.31)
Also tried an MTTY Task 29, reload of MAGLDR then re-flash of the NAND in case traces of my previous ROM were still around but that hasn't helped either.
Any ideas?
I seen many threads about same situation. Actually i itself use daily gpc hd2 gingerbread v1.5 with same problem. Sometime help back button (when call ended not at me). Sometime just more light to proximity (or it light) sensor (when inside and put phone with face to some light). Outside i just must turn phone with face to sun or good light then screen wakes up.
I tested many many nand roms. All have same problem.
Tested win 6.5, win 7 and sd version, they works well. That gives confirmation that my proximity (or it light) sensor works well. And finally that something wrong with nand.
Here was discussion that MAGLDR does that. NO.
I started run over net and find solution. Here seems no help for this right now. Maybe just problem ignored because cookers itself dont have this and cant do anything. If you dont have problem then how you can fix it.
On web i found some discussion about kernel problem or smth about this proximity sensor. I cant find it right now again. There was talking about this problem, but no solution.
I thinked about open new thread and invite kernel chiefs to discussion to solve this problem. But today i find your ask. I opened for any test and help that i can give. I dont be afraid to lose my phone if something must go wrong. Phone is just piece of electronic and you can replace parts. But knowledge and experience you cant buy.
Any ideas how to resolve this little bad thing?
Thanks for the reply.
Yes it's a real problem but mine won't wake up no matter how much light.
The only way I can get it to wake up is to plug it in to power, then the screen wakes up.
Is that the same as yours?
I i remember it right i was suprised once too if this happened. I just put my "again dead" phone to charging and its waked up.
If screen is dead and same time connected to pc (i use for managing inside phone androidcommander) then moving over dirs wake screen back too.
But lets look how long my nerves will be good. Today i thinked to move back win 6.5 and sell this bastard.
No don't sell we need to resolve! I'm hoping someone will look at this thread and help us figure out why this is happening. I can't believe we are the only 2 people who have this issue.
Anyone else have any ideas as to why this is happening?
This issue was also on sd versions. So I see nand has not fixxed it. I am running MDJ HD 4.6 and have this issue. Sometimes the light sensor works properly and other times it goes to black screen and gets stuck.
I read somewhere that it might be the hardware itself. Saw a video on youtube also. Seems the european T8585 and telstra T9193 might have poor light sensors. The T-mobile light sensor supposedly does not have this problem.
So I am guessing anyone with this problem does not have the T-mobile USA version??
It could just be drivers too. It is a pain and sometimes I wish I could just disable the light sensor.
Also NAND roms are no better than sd versions as far as bugs. If the sd version has the bugs then so will the NAND version. The build is just installed at a different location.
Yes good point.... the bug will be replicated as it's just where the OS is stored that's different.
I'm thinking it's the hardware as I have this problem on WinMo6.5 too and I have tried various WinMo roms but had the same problem.
Mine is a UK HD2 supplied by O2. Wish there was a fix for it :-( It's a real problem.
PS I ran PhireMOD's Skinny EVO SD Android for a while and didn't have as much as a problem as I have had with the 2 NAND roms I've tried..... if that's any clue? At least with that rom I was able to make calls and hang up and still get the screen back after I hung up (except for the screen going white and washed out which could only be resolved by a reboot). There was still the problem with the screen being on all the time during a call or the screen being black and not coming back on during a call though.
I have these sort of problems too. It's really annoying when you're in a phonecall and you take the phone away from your ear and it takes a few secs to turn on. Also when I'm unlocking it.
Sent from my HTC HD2 using XDA App
At least yours comes back on lol mine stays off for ages and ages and sometimes doesn't come back on at all!
Noticed that if I shine a torch into the proximity sensor that's the only way I can get the thing to turn back on :-( Also noticed the 2 little holes where the prox sensor sits appear dirty/cloudy... not sure how that happened.
I wonder if the prox sensor is busted or if it's just dirty or something? Going to get a T5 Torx and take my phone apart to find out if it's something I can resolve.
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Hmm, are you sure g9650? Seems my guess about kernel was then true. I use gpc pure gingerbread 1.6 with gpc itself made kernel. I go right now replace kernel and test. Results tomorrow.
Took the phone apart yesterday night and uncovered the proximity sensor. Even out of the case it needs a torch/flashlight to shine on it to bring the screen back on :-( I honestly think the proximity sensor hardware isn't working anymore.
I'll try the kernal you suggested though just in case that's what's causing the problem.
Datas0ft let me know if it works for you?
Latz, actually i taked to test markinus extra clean 1.7.1 (right now on it itype this). Had one call before and no changes.
Also i stuck on taking out kernel at this version. Low knowledge. Dont find any help yet on xda. I work on it. If you have hints dont hestitate say.
Sent from my HTC HD2 using XDA App
:-( I was hoping we found a miracle cure! Ok let me flash mine tonight and try it to see if mine behaves any different. Will post back with results... let me know fi anything changes with your phone datas0ft.
q9650 said:
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Click to expand...
Click to collapse
Can anyone upload MarkinuX Kernel please? Thanks
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Thanks, I just finished downloading the whole Markinus rom to extract kernel haha but you saved me... will test and report, thanks
datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Quick question, the zip file you gave me only has two .ko files and zImage while the original rafdroid kernel has like 5 .ko files... what should I do? copy raf's kernel .ko files missing into markinux ones?
Or just pack the zip file using two .ko files? Thanks
I cant ansver. Dont have much knowledge on this. I followed instructions. This taked to me these three files. I installed these.
I finded some problems right now (wifi and gps dont work and my 3g too). This may not happen at kernel side. I have made some changes on rom side. I go replace whole rom and then again kernel. Then i go make final decisions.
I'm having the same problems, you two are not the only ones. This has been really frustrating me lately, and I thought it might have been a problem for only me because I just had the screen replaced. It worked fine in winmo 6.5, now in NAND I'm having some issues. I text a lot more than I actually call, however so it's not that big of a problem for me right now

Weird HD2 unresponsive screen

Now I've read about a problem of the hd2 having digitizer problems and that only a replacement will fix the unresponsive touchscreen issue. But why is it that when I can get my touchscreen to work that it works flawlessly until it goes to sleep? Then i have to continually wake and swype and sleep over and over until it responds. It just seems very weird that after it wakes that it never seems to have a problem. I'm using the miui rom right now and have set the screen to never go to sleep. So I want to see how long it will go without this problem. Has anyone else seen this happening with their phone as well?
Make sure the kernel, and Rom are up to date.
I have that too on an AOSP Gingerbread rom. The screen is not unresposive per se but calibration seems off some times, strage for a capacitive screen.
ive had the problem with android before and there were a few different fixes ...
one fix was to turn off compatibility mode
another was kernel
ive also had the problem with wp7 ( nothing a few hard resets and patience couldnt cure )
either way good luck
well since my first post, i hadn't let the phone go to sleep once and it worked perfectly fine. so i decided to turn off compatibility mode and let it go to sleep.... and when i woke it and i slid my fingers down it actually worked. so far it's worked every time. why would compatibility mode mess up the touchscreen though?
i have NO earthly idea! just a little tidbit i picked from a dev. i would speculate but would end up looking and sounding foolish. so im going to quit while im ahead and have actually been of help :-D cheers
Where can i disable compatibility mode?
I get the same problem. I've used a ICS rom for a day or so and suddenly the lockscreen was unresponsive. I thought it was ROM problem, so I flashed Cyanogen 7, but the screen didn't respond as well... I flashed everything to stock (removing magldr and hspl) and the problem stayed... After several restarts the screen started to respond and now it works (sort of). The tricky thing is: sometimes when I go out from some app in android, the screen doesn't respond again. Locking and unlocking the screen fixes this, but only temporarily.
Did this ICS rom screw something (...hardware?!) or is it a pure coincidence that a few people encounters the same problem for the first time in such a short period of time...
And one more thing... my warranty expired 5 days ago... please help!!!
I had this same problem with my phone before my warranty expired; before I flashed any android roms on it, and while it still had stock WM6.5. I called HTC customer support and they had me send in the phone for repair. They replaced the digitizer and I haven't had the same problem since. It was wierd because in my mind is seemed like a software problem because it would respond nicely as long as the screen was unlocked and the instant it was locked the response was very crappy, sometimes it took forever to unlock my phone. So it might somehow be a hardware issue
WaspVL1
Machupichu2 said:
Where can i disable compatibility mode?
Click to expand...
Click to collapse
spare parts!
I repair phone myself and i can say that i get A LOT of hd2's with this problem. For the most part it is the hardware because no matter what software you put on the phone it is just a matter of the luck you have to get it working. My hd2 broke 2 times b4 and it was always hardware. Htc must of messed up with the hd2 digitizer
cmacia06 said:
I repair phone myself and i can say that i get A LOT of hd2's with this problem. For the most part it is the hardware because no matter what software you put on the phone it is just a matter of the luck you have to get it working. My hd2 broke 2 times b4 and it was always hardware. Htc must of messed up with the hd2 digitizer
Click to expand...
Click to collapse
from what ive seen in photos of the leo mobo it looks like the connection for the screen/digitizer (not sure on hardware) is located right behind red end call/power button and from being mashed off,on,off,on,etc loosens/damages connection.
or is the hardware screen issue just a complete shot in the darks chance?
OH ... ive had the software issue (fixed as i mentioned earlier) AND unrepairable (with my limited tools and balls to physically tear into this badboy) hardware issues.
well, it's been a few days and my phone still seems to be fine. it hasn't once locked up on me yet. i don't know why turning compatibility mode would fix this. or maybe the phones connectors were loose and are now miraculously back in at the same time i unchecked compaibility mode. the only bad thing was that this was happening the last couple weeks and i had given up and already ordered a sensation 4g. or well, guess i have 2 phones now
Its seems possible. Every since I replaced my digitizer with a non OEM one its has never failed on me again. And I hope it never does. There dam expensive.
rubledub said:
from what ive seen in photos of the leo mobo it looks like the connection for the screen/digitizer (not sure on hardware) is located right behind red end call/power button and from being mashed off,on,off,on,etc loosens/damages connection.
or is the hardware screen issue just a complete shot in the darks chance?
OH ... ive had the software issue (fixed as i mentioned earlier) AND unrepairable (with my limited tools and balls to physically tear into this badboy) hardware issues.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
Compatibility Mode
I also have this issue, therefore I just recently flashed my hd2 with Tytung's 4.0 ICS Rom. As expected, this didn't help very much.. What I am now going to try before I send my phone to HTC is to disable compatiblity mode. BUT, I can't seem to find this compatibility mode check anywhere. Could someone please guide me there?
..
Windows 7
I will be flashing my phone with w7 now, to see wether this is an android kernel bug / softare issue or if this relates to hardware. I also see a lot of people saying that after fixing the digitizer it works again, so it might actually be a hardware issue. I will post my feedback when I have tried with w7.

[Q]Part of touchscreen not responding

Hi
A few months ago (november) I noticed that a part of my touchscreen wasn't responding when I touched it. (3-4mm on the right side) I asked here for help but you advised me to send it back. That's what I did on the 17th november.
Yesterday, more then 7 weeks later I finaly got my phone back. I was really happy but when I noticed the problem wasn't solved, I coudn't believe it. The only thing they have done to my phone is the following:
-Reset everything
-put the U8800V100R001C00B135SP01 firmware version on it. (I updated it before to 136 oversea)
Now I don't know what to do. There was no letter delivered with the phone with more information.
May update to 2.3.5 solve the problem? I have a synaptics touchscreen.
Thanks in advance and sorry for my bad language.
Usually when the digitizer fails you loose a large percentage of the screen touch, like 25% or more percent, not less than 2% that you seem to be missing.
So either the service personnel wasn't thorough enough to check the digitizer and thought that the phone was ok so you got it back as is, or there isn't really a problem...
If you post a video we might be able to say which case is which, if it is the first, complain and ask for a replacement.
I have the same problem too.
I found out this problem after my baby lick on my phone, was her saliva short circuited something inside?
About less than 10mm on the right side was not responding. I realized this when trying to type the right side of the virtual keyboard and weren't able to type letter 'o', 'p' and other button in that area.
Is this means that my digitizer is broken? I think I have experienced this in the past, but maybe it went to normal again without me noticing it.
Try a costume ROM. I had a shaking screen when I longed pressed it. This happened with the stock froyo rom, oxygen, MIUI and the old cyanogenmod. I have no problem with the current DZO's ICS rom.
tiagol11 said:
Try a costume ROM. I had a shaking screen when I longed pressed it. This happened with the stock froyo rom, oxygen, MIUI and the old cyanogenmod. I have no problem with the current DZO's ICS rom.
Click to expand...
Click to collapse
Hmm, not too keen to change the stock froyo rom as I use my phone for work such as using my work email etc. Don't want the extra hassle to try out some roms.
Maybe I just send it to the distributor. Thanks for responding.
Moved To Q&A​

Take that multi-touch! Fix and lock in what works for YOU regardless of updates

By 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
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
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
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
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.
very interesting! lots of FC after loading the file, cant really "Power off using power button" because of FC-windows, using adb reboot instead.
current ROM: [ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 10-TEST][2013/08/27]
ts-10: no more jumping in google maps while zooming/panning, but still jumping in other apps. after second reboot, starts jumping in maps again. after third reboot, no jumping on rightside of screen.
screenshot using two fingers
ts-20: lots of jumping on right side of the screen, zooming/panning in gmaps is still jumpy. after third reboot, still jumpy in gmaps.
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, same effect. after third reboot, still jumpy on right side of screen.
so what exactly are in those files?
neonlite said:
very interesting! lots of FC after loading the file, cant really "Power off using power button", using adb reboot instead.
tried ts-10. no more jumping in google maps while zooming/panning, but still jumping in other apps, will try others.
so what exactly are in those files?
Click to expand...
Click to collapse
When you say lots of FCs, can you tell me what ROM/version you are running?
You should IGNORE any instability in that first boot. While you can boot into android using the files I'm providing (and in some cases run fine), there could be mismatches in versions depending on what you have currently installed, which is why I say in RED you must reboot at least once before the system will become stable.
Once you do that reboot, you are back on your original software with just the touchscreen controller updated.
neonlite said:
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, seems most stable.
Click to expand...
Click to collapse
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.
sfhub said:
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.
Click to expand...
Click to collapse
yes, ignored all FC's. no problem.
ts-10 is running perfectly, no more jumpy stuff. maps/right side of screen, hold and drag working great too.
I really appreciate how much effort you've put into helping others with troubled devices here.
Could we get some clarification on what exactly the 3 packages are? Are these touchscreen settings customized by you or simply the settings from each of the 3 versions of 4.3 we have had available to us?
You sent me here from the other thread and i must thank you, the ts10 one worked fine and now no screen problems, cancelled my replacement. Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
It is the touchscreen controller software.
pashinator said:
Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
Click to expand...
Click to collapse
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
sfhub said:
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
Click to expand...
Click to collapse
cool i thought i broke it by bashing it to get the screen to work again
i've been a long time lurker at the xda forums and your multitouch fix made me register and become a member just to say thanks. ts10 fixed my multitouch issues, going to observer for a few more days and update you if there are bugs. thanks a lot!
My tablet was working perfectly on the JSS15J then JSS15Q came along and I found letters "sticking" while typing and the screen was unresponsive to touch while laying flat on a table. I flashed the ts-10-lock image and so far, so good. I have been typing for awhile now with no "sticking" letters, and while laying flat on a table. I have not encountered the unresponsive screen at all flat on its back or otherwise. I will continue running through scenarios that used to give me problems and report back if I encounter anything. Also, running Bulletproof kernel and no impact with kernel functions.
Thank you sfhub!
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
This is the video of my N7 placed on my MBPs' keyboard.
http://www.youtube.com/watch?v=H05N1P0dpTo
Can this really be only a software problem?
I am not really experiencing other touchscreen issues with my N7 except for some very rare stuck touches. This one I triggered by accident.
bandit_knight said:
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
Click to expand...
Click to collapse
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.
Excellent.
I'll try these now and put them through there paces.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Great work
Incredible!! tried the ts10 and OMG everything is fixed!! Great work, sfhub!!
you should work in Google, seriously! shouldnt he, everybody?
My device is:
1) 4.3 JSS15Q
2) two finger touching registered as one finger, and muiti-touches ghosted. hold on the Left side of screen and the touch is registered repeatedly
1) TS10
Yea I booted 10 first and it is great. I can't reproduce any of the bugs I've seen before using YAMMT.
Google Maps Pinch/Zoom is working flawlessly. I couldn't even zoom in before.
The OP says to "fastboot boot boot-ts10-lock.img". Should we eventually "fastboot flash boot-ts10-lock.img" to make it permanent?
My N7 is:
HW rev_e
Bootloader....... FLO-03.14
15Q - CM 10.2 Kanged Build 9
Sitting the N7 on my Logitech Keyboard doesn't make it go crazy either! LOGITECH FTW
sfhub said:
It is the touchscreen controller software.
Click to expand...
Click to collapse
How do you "lock" it in so that it won't get updated? Is it just a file in the filesystem, if so how do you prevent "fastboot erase" from getting rid of it? I've looked at ektf3k.c and know where I need to make a change so that it will replace any non-matching version, but I don't really know where the actual firmware is stored. It doesn't seem to be in the vendor part of the kernel tree or in the actual ektf3k.c or ektf3k.h files. Where is it kept? kept in fw_data.b
I'm new to Android, but I'm not new to Linux or reverse engineering so please be patient with me. Just looking for a technical description of how you did what you did. What exactly is in the .img files?
EDIT: I haven't booted any of them yet, but I'm guessing these are Linux kernel images with a modified version of the elan driver. Sorry for being stupid, I'm just trying to put this all together in my head and I can't cope with anything that seems like magic. Thanks for your time.
EDIT: Ok, I figured out where the firmware is stored. I also successfully built a ROM with my compiled kernel and flashed them to the tablet. No brick, it booted the second try and seems to work. Of course there's no apps on it hardly.
I'm kinda thinking out loud here, please correct anything that I get wrong:
I started off with the assumption that there was a closed source driver, but that seems to have been incorrect on my part. After looking at the code a little more, I see that ektf3k.c appears to be the lowest level driver, outside the embedded firmware. The driver does only update the firmware in the case that the flash is empty (FFFF.....) or the firmware presented is a higher version (just as you said of course). It appears that a simple change will make it flash any version presented that is different than the one currently flashed in. I plan to try this on my tablet and see if there are any unexpected repercussions from doing so.
I wish I had a datasheet for the controller (hint hint anyone).
DISCLAIMER: I know that you have already solved this problem in an arguably better way, I just want to tinker around a little. Thanks again. :good::good::good:
sfhub said:
By 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?
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
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
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 able to get 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):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies.
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
you can find adb/fastboot drivers HERE
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
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
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
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
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.
Click to expand...
Click to collapse
So if we do this can we lock the boot loader backup. If for some reason it doesn't work will I be able to take it back for exchange. After unlocking the boot loader. Do people leave the boot loader unlocked . Is the software staying the same meaning will I be ok downloading future updates.
Is there a way to find out what variance is installed right now on the device? I got JSS15Q and my tablet is useable but sometimes there are ghost touches or the touch is stuck or gets interrupted and the likes.

Categories

Resources