yashsingh1/xdaforums huggingface dataset:
[ONE Q&A, Help & Troubleshooting] Ok_Kaleidoscope5109:
To me its a night and day difference. The old fixes didn't do crap IMO. This is the real fix. Not sure if its 100% fixed. Need to compare with other devices now but the performance is far better than before for sure.

Sent from my OnePlus One
[ONE Q&A, Help & Troubleshooting] zephiK:
Update your kernel, ak kernel already has the new firmware (beta 040) and Franco will have a update today with the new firmware (r17).

Or wait for your ROM to update their ROM/kernel.
[ONE Q&A, Help & Troubleshooting] bradm23:
Sadly for me Franco R17 didn't fix my touchscreen issues. I can't type at even a decent speed without getting miss letters or the occasional swipe even though I didn't swipe. I have had a trouble ticket in with one plus for three weeks already! I have also used a friends 1+ for two days and typing was flawless compared to what I have been dealing with.

I opened a pay pal dispute to get my money back, however I did send one plus an email giving them one week to help me with a replacement before sending mine back which is only fair since this firmware didn't fix my issue and it is def faulty hardware. I really like the phone and really enjoyed using my friends when it was actually working as intended.

Hopefully one plus will stand by their customers and help get this replaced. I personally would stop giving out invites until you have fixed previous buyers issues. Pay pal said if they get enough disputes they will close their accounts.
[ONE Q&A, Help & Troubleshooting] Perilla_:
R18 fixed my problems.

A new synaptic driver have been released, and this driver really fixed my problems. The phone looks completely different.

Enviado desde mi A0001 mediante Tapatalk
[ONE Q&A, Help & Troubleshooting] Elvecio:
Did you have fast-typing problems with the previous driver?

Inviato dal mio A0001
[ONE Q&A, Help & Troubleshooting] Perilla_:
Yes, it was responding slow, now it's perfect.

Enviado desde mi A0001 mediante Tapatalk
[ONE Q&A, Help & Troubleshooting] S M G:
Any word yet on the next CM11s update (36R ???)
[ONE Q&A, Help & Troubleshooting] harrys1991:
not had any problems with typing fast so far.
[ONE Q&A, Help & Troubleshooting] Schrotty35:
I have install latest ak kernel and the touch problem are not solved. Whene i write a message the space taste not work correct.

Gesendet von meinem A0001 mit Tapatalk
[ONE Q&A, Help & Troubleshooting] stu5797:
Guys, there is not a fix for this until one plus addresses it. There is no magic kernel either. If for some reason you don't have ghost touches just wait and they will come back. Be patient and hopefully it will be fixed properly.
[ONE Q&A, Help & Troubleshooting] zephiK:
First of all, OnePlus doesn't need to address anything because the fault isn't due to code fault on OnePlus/Cyanogen's part, they've already addressed that they can't do anything since the the issue relies upon Synaptics, the company that provides the touch screen drivers http://www.synaptics.com/

Secondly, the problem is already fixed in the new touchscreen firmware. It is expected to come out in the next OTA which is still being finalized and tested as mentioned by Cyanogen. The fix is already obtainable through using custom kernels which contains the new drivers. Its not kernel magic, its a problem that lies within the drivers.

Third, they don't magically appear back again. Its a problem with the drivers which has been already fixed but not yet delivered to the masses in OTA and is only retrievable through custom kernels.
[ONE Q&A, Help & Troubleshooting] jlevy73:
Always have a ton of a respect for you but I have to disagree with you regarding your point #2. The updated drivers do not fix the problem for me nor for many of the people that I know with a One+. I would gladly welcome a fix but the updated firmware did not solve the problem.
[ONE Q&A, Help & Troubleshooting] zephiK:
Well sadly to say, it fixed the problem for me as well as a large number of other people. Theres probably room for improvement and it may come in the future. For the ones that the firmware did fix the problem, its great and I experience absolutely no problems. I hope it gets resolved when it fully finalizes. Just for me, it seems perfect to me and I have no problems typing super fast even with SwiftKey Flow enabled.

Have you tried a factory reset with the new kernel? Or using another ROM to have the latest updated CM ROM commits as well as the latest CM Kernel commits?
[ONE Q&A, Help & Troubleshooting] stu5797:
Thanks zephiK for your respectful reply. Also thank you for all your input on these forums. I guess I have tried all kernels and multiple roms only to find this issue when running swiftkey. I will try out a differ keyboard and maybe that will help. Sorry if I sounded disrespectful talking about magic kernels but I do respect everyones work since they are doing it for free out of their own personal time. It is just a very frustrating issue that hopefully can be resolved but there obviously is more behind the scenes here. It is a horrible problem that they cant seem to fix.
[ONE Q&A, Help & Troubleshooting] zephiK:
Didn't find you to be disrespectful at all. All I'm saying is that, in my own personal experience the new touchscreen firmware does indeed fix the problem for me. I understand the frustration, it really is annoying but for the most of us it is indeed resolved. But setting that aside, lets take a look at what you can personally do and to rule out other factors that could possibly cause your touchscreen not to function properly as for the most of us it does work.

If it didn't work for you, then I highly strongly recommend you,

1. Flash a custom ROM if you haven't. Preferably one with the latest CM ROM commits. Remember, those newly CM kernel commits could possibly not be playing nice with outdated commits (especially if you're running CM 11S).

2. If you're already using a custom ROM, do a factory reset. Start from scratch including the wipe of /system/ (its not wiped manually in TWRP). The importance of this is that if you're going from AK to Franco, AK kernel related files will still remain in /init.d/ such as 00ak, 99zram. Stuff remaining from flashing UKM or whatever.

....... once you finish wiping everything, try and reproduce the problem with MINIMAL applications. Use a basic texting app, your preferred

keyboard app (I use SwiftKey and have no problems, enable SwiftKey Flow as well so you can see if the problem occurs or not).

I also use PA Gapps PICO. Which is found http://xdaforums.com/showthread.php?t=2397942 -- gapps would probably not affect anything but hey, might as well flash it to see if it happens.

And don't forget to use Franco r19 or whatever kernel you use. I'm sure ak has the commit included as well, I personally prefer Franco.
[ONE Q&A, Help & Troubleshooting] Schrotty35:
I dont like franco. I use AK Kernel and i have make full wipe and use latet cm11 nightly (have also test other cm roms) and the write problem not fixed sorry.
[ONE Q&A, Help & Troubleshooting] SenK9:
I'm using the 0913 CM nightly and AK's v40 kernel, and the dodgy screen touches are gone. They used to happen 80% of the time for me when typing on the keyboard.
[ONE Q&A, Help & Troubleshooting] PiTXI:
Using Franco kernel v19 , after factory reset/wipes and same issue here.

We need a solution
[ONE Q&A, Help & Troubleshooting] zephiK:
It doesn't matter whether or not you don't like him or his kernel. Just try it and see if any changes are done using his kernel.

The whole point is to try trying different setups because obviously your set up isn't working when other people have absolutely no problems with typing fast on their phone.

It's either that or your typing isn't accurate. Take a video demonstrating your typing problem and show that you're using the latest kernel. Post it on jira so the cyanogen team can look into it and forward it to synaptic.
[ONE Q&A, Help & Troubleshooting] norpan111:
Oh god I thought I was the only one with this issue! In going insane! Let's hope the ota is just around the corner
[ONE Q&A, Help & Troubleshooting] Elvecio:
I'm on the latest nightly of cm11 and the typing problem still occurs.
[ONE Q&A, Help & Troubleshooting] cymbaline24:
I believe they have really improved the accuracy so far, but I still have a typing issue. When typing, for example, "the", it comes out "he", even though the screen does register that I tapped the "T" (I have the option to show touches turned on). It's like the software ignores that I hit that letter. I'm not sure if it's an issue of hitting one letter too soon after the other or the fact that they are close in proximity on the screen. It's annoying as hell though. I switched to the CM nightlies and still experienced problems, so I've tried the latest AK kernel and Franco kernel and it STILL happens. I've tried many different keyboards too. I don't really want to switch ROMs, but does anyone think there's a chance that could fix it?
[ONE Q&A, Help & Troubleshooting] Elvecio:
I'm in the same situation and no, I think that it's hardware related.
[ONE Q&A, Help & Troubleshooting] cymbaline24:
See, I was starting to think it was hardware too, but seeing the touches register on the screen even though they are ignored made me think it was software again. But I'm a novice, not an expert, so who knows? I just wasn't sure that another ROM would make a difference if 3 different kernels didn't. I may try PAC-MAN anyway...
[ONE Q&A, Help & Troubleshooting] Elvecio:
The fact is that I tried 2 others Oneplus Ones and they haven't any problem.. If it's software related, it has to be an issue of the 100% of the products.
[ONE Q&A, Help & Troubleshooting] cymbaline24:
Hmm, well, I guess that settles it. Do you think I can send it back for repair/replacement if I wasn't the original purchaser? I bought off of Swappa.
[ONE Q&A, Help & Troubleshooting] Elvecio:
I don't know for your situation, you have to try I guess.
[ONE Q&A, Help & Troubleshooting] oscarandjo:
Even if it is covered by normal OPO RMAs they won't RMA it until the next update is out. They refused to RMA mine until 36R is out *mid October* - I have to wait half a month! I think they are delaying the inevitable so people can't file PayPal charge backs. I don't know what to do. I love this phone but typing is a Royal pain.
[ONE Q&A, Help & Troubleshooting] jlevy73:
I have been trying to RMA the device since late August and they have done an excellent job of stringing me along. OPO's customer service has been simply abysmal. I used a credit card and am thinking of just putting the charge into dispute as fraudulent then OPO can explain to VISA why they can't get their head out of the arse.
[ONE Q&A, Help & Troubleshooting] cymbaline24:
It is a huge PITA - I'm freaking jealous of all the people who managed to fix their touchscreen issues, lol. I'm trying to teach myself how to type differently so as not to trigger the issues *sigh*. Maybe swyping would be a good workaround, but I just can't get into it...I've tried many times.
[ONE Q&A, Help & Troubleshooting] norpan111:
Yeah this issue makes the phone completely trash for me and all I can think of is I want another phone. This issue should be agnowled and fixed asap. Such a big turn off
[ONE Q&A, Help & Troubleshooting] jlevy73:
It has been acknowledged: https://jira.cyanogenmod.org/browse/BACON-55

Sad part is the ticket was opened over 2 months ago and they have not resolved the problem.
[ONE Q&A, Help & Troubleshooting] shiftf7:
wow - I'm glad (and extremely sad) to hear that I'm not alone regarding the recent franco kernels not doing a damn thing to fix my touchscreen issues as well. Even after franco r22 for me - I'm STILL getting touchscreen issues. And like the rest of you - they refuse to RMA for me until the update is out. Freakin annoying.
[ONE Q&A, Help & Troubleshooting] cymbaline24:
Ok, stupid question... Everyone keeps talking about the new update fixing the touchscreen issues, but if the CM11 nightlies didn't fix it, why would the newest stable release fix it? Isn't CM11s based on CM11, just with the Google-stamp-of-approval? Or is that thinking totally wrong? Because then I think about how if you flash a different kernel there is a different release for CM11S as opposed to other ROMs...
[ONE Q&A, Help & Troubleshooting] Quixventure:
Just tried the Franco Kernel v22 (getting 23 now...) and my touch issues are significantly improved.

I still have a lot more trouble on this than I do on some other phones, mostly with hitting space bar, but my accuracy was greatly improved when I moved over to Franco v22... Had to wipe the phone and its possible that helped too, but if you have the issue and have not tried Franco, give it a go...
[ONE Q&A, Help & Troubleshooting] cymbaline24:
I tried Franco r22 a few days ago...had a weird glitch - a horizontal blinking line would come up ever so often. Didn't notice any improvement in touchscreen, so I tried the latest AK kernel, v50...no glitches, but still no change in the touchscreen. I'm on SlimRom 4.4.4 build 8.2 (dirty flashed over build 8.0). Am now noticing some force closes, so I'm gonna keep trying different combos of ROMs and kernels - crDroid and Heisenberg are next on my list. And of course whenever the latest CM11S update finally shows up I'll try it too, lol. I've pretty much tried anything anyone on any forum has ever suggested would fix it, within reason. At this point my only real problem is typing two letters in quick succession that are near each other (it will ignore one of the letters), although sometimes I think it still ghost taps a few extra letters in there for me. ;)
[ONE Q&A, Help & Troubleshooting] Schrotty35:
Same problem with touch issus on fast typing.

Gesendet von meinem A0001 mit Tapatalk
[ONE Q&A, Help & Troubleshooting] cymbaline24:
I am amazed and thrilled! I flashed the new LiquidSmooth Lollipop ROM and the fast-typing issues have apparently disappeared! I just typed 4 long sentences as fast as my thumbs would go and there was not one mistake. :D
[ONE Q&A, Help & Troubleshooting] PiTXI:
same problem already with 44s and franco kernel #35
[ONE Q&A, Help & Troubleshooting] paniro187:
Mine went away when I flashed calkinlins (sp?) Stock rom. Hasn't been back since
[ONE Q&A, Help & Troubleshooting] PiTXI:
What is calkinlins??
[ONE Q&A, Help & Troubleshooting] Poser:
Interesting ... I have had my phone since November, and did not have this issue. However it should appeared out of the blue today. Bummer
[ONE Q&A, Help & Troubleshooting] nomboly:
If you haaaave to type large texts set min freq to 1600-1800mhz and bam lag is gone...
[ONE Q&A, Help & Troubleshooting] JHOSMAN:
I could say whether this result is normal? -
[ONE Q&A, Help & Troubleshooting] mapolidori:
Is anyone else getting the error below after trying this? Parts of my screen will randomly stop detecting touch. Mostly the bottom hardware buttons and a large rectangle in the middle of the screen. The cat baseline_test from the bacon 55 thread solves my problem immediately for a day or longer, but I see this error in the baseline_test file. Any ideas?

trx-to-trx raw readback: 0 0 0 0 f0 3

trx-to-trx test error: data_buf[3]&0x07 =0 data_buf[5]&0x3f=3

imageid=0x14001222,deviceid=0x14001222

1 error(s).
[ONE Q&A, Help & Troubleshooting] red71fl:
Got this from mine.

u0_a146@A0001:/ $ su

root@A0001:/ # cat /sys/class/input/input0/baseline_test

1++ raw_cap[05][05]=1779 is not in range[0946~1757].

2++ raw_cap[05][06]=1810 is not in range[0942~1749].

3++ raw_cap[05][07]=1791 is not in range[0937~1741].

4++ raw_cap[05][08]=1758 is not in range[0933~1733].

5++ raw_cap[05][09]=1725 is not in range[0928~1723].

6++ raw_cap[06][05]=1823 is not in range[0947~1758].

7++ raw_cap[06][06]=1806 is not in range[0942~1750].

8++ raw_cap[06][07]=1794 is not in range[0937~1741].

9++ raw_cap[06][08]=1767 is not in range[0933~1733].

10++ raw_cap[06][09]=1734 is not in range[0928~1723].

== Reach max error count (10), stop test.

imageid=0x14001222,deviceid=0x14001222

10 error(s).

root@A0001:/ #
[ONE Q&A, Help & Troubleshooting] haxpak:
error

well i tried this on my phone but the cat displays this:

root@A0001:/sys/class/input/input0 # cat baseline_test

1++ raw_cap[01][04]= 22 is not in range[0805~1878].

2++ raw_cap[01][05]= 18 is not in range[0801~1870].

3++ raw_cap[01][06]= 21 is not in range[0798~1861].

4++ raw_cap[01][07]= 12 is not in range[0794~1853].

5++ raw_cap[01][08]= 14 is not in range[0791~1846].

6++ raw_cap[01][09]= 14 is not in range[0786~1833].

7++ raw_cap[01][10]= 15 is not in range[0784~1828].

8++ raw_cap[01][11]= 15 is not in range[0782~1824].

9++ raw_cap[01][12]= 11 is not in range[0777~1814].

10++ raw_cap[01][13]= 11 is not in range[0776~1810].

== Reach max error count (10), stop test.

imageid=0x14001222,deviceid=0x14001222

10 error(s).

any ideas anyone?
[Verizon HTC One (M7)] bader.chohan:
Hi, I recently buyed HTC one with sense 5. Can somebody help me to update my device to sense 6 legally. I mean official update. I'm ok with rooting unlocking bootloader. Etc. My last device was Samsung galaxy custom slimrom But in the end I want HTC with official stock version.

I found one updatepackage.zip and try to update it with recovery. But was unable to get in recovery mode. After selecting recovery in bootloader HTC sign appears and screen turns black for few seconds and it restart the system.

Can anybody guide me? Thankyou in advance

Bootloader photo:

http://www.yogile.com/npqx8b6i/41m/share/?vt=4PLxQt9
[Verizon HTC One (M7)] woodsman4:
connect to wifi and go to "Settings > Software Updates"
[Verizon HTC One (M7)] bader.chohan:
Thanks for reply. But software update is disabled. It says only in cdma mode.
[Verizon HTC One (M7)] bader.chohan:
Bootloader photoView attachment 2872270
[Verizon HTC One (M7)] bader.chohan:
View attachment 2872283
[Verizon HTC One (M7)] woodsman4:
well, then i guess you're up a creek. it's not a good idea to buy a phone that's not from your country. that would be like me buying a phone from the UK even though i'm from the US
[Verizon HTC One (M7)] bader.chohan:
I know it was cheap that's why. I need suggestion or guidance??
[Verizon HTC One (M7)] bader.chohan:
I want sense 6 on my HTC by any means. Please somebody guide me how to or refer me some link.?
[Verizon HTC One (M7)] leech28:
http://xdaforums.com/showpost.php?p=54132389&postcount=2

but first s-off it. using firewater and never s-on it again otherwise you'll get stuck!!

http://xdaforums.com/showthread.php?t=2703585
[Verizon HTC One (M7)] bader.chohan:
Thanks leech28 for the reply. One more thing, does s-off means like getting root Ur just unclocking boatloader.

And one more question, I found thread with official sense 6 updatepackage.zip. Is it possible to update my HTC to sense 6? Will it work for me. If yes then I will be very thankfull if you guide through that or help me with link. :D
[Verizon HTC One (M7)] Uzephi:
S-off is more dangerous than a regular unlock. When the secure flag is off, you can flash anything to any partition. You can even flash unsigned things like decrypted ruu files... Which is what you would need to attain sense 6 when not on Verizon towers. We do not have an official sense 6 ruu from HTC directly, only the decrypted one which is why you should stay s-off in case you would need to ruu again.

For the ota zip, you would need root anyway to put the file into the correct directory to update. Might as well just s-off and ruu. It would be less of a pain than moving the ota file and setting correct permissions.
[Verizon HTC One (M7)] leech28:
S-off means security off this means you will be able to flash any ruu even if it is not encrypted, ill recommend you s-off it as it will be easier to update your phone in future s-off dose not root it's just a security feature to protect phone from modifications
[Verizon HTC One (M7)] bader.chohan:
hmm. Got it. And If I update and then s-on it. What will happen. Will it brick my htc?
[Verizon HTC One (M7)] Uzephi:
No, it will not, but I highly suggest starting s-off until an official encrypted ruu is released. If you ever run into an issue and need to ruu while s-on, you would be sol.
[Verizon HTC One (M7)] ccarr313:
S-off will allow you to do anything. Flash custom recoveries, flash firmware, flash roms, flash zip packages(like root).

Use weaksauce to gain temproot then firewater to get s-off. There is a pinned thread on how to do it in the original development section.

Once you do that, you can flash any rom you want, I personally recommend Santod's GPE 4.4.4, or CM11, or Nusense 6 depending on your taste.

Also - there is no reason to EVER go back to s-on. S-on just means you don't have access to the system. Being s-off will not prevent you from doing anything with the phone, and will allow you to load any RUU file in case you f up your bootloader somehow. The ONLY reason to ever go back to s-on, once you attain s-off, is to return for a warranty replacement if you end up with a hardware defect down the line.
[Android Q&A, Help & Troubleshooting] kishana:
Sir paano ko po maroroot ang lg l3 e425 ko...pahelp po please
[Windows Mobile] saad.khan6670:
So here its I decided to root my phone samsung infuse 4g using odin but when I did I stuck on the at&t bot screen so when I again connected my phone to computer to go back to stock using one click it doesnt even work nor my phone now goes on download mode and now its not even starting up i have tried every thing but it is just stuck on this screen every time
[Moto X Q&A] Vebr137:
Hi. Sorry to bother - didnt find an answere. I have Moto X from ATT ( Android 4.2.2). It was rooted by seller - so I recieved it as it is. Now I want to install 4.4, but at first I need it back to factory. I've tried to wipe it from menu - nothing. Its reboot and nothing happends. Ive tried to do it from recovery - it's just rebooting and its it. Help please
[Moto X Q&A] Verttex:
Have you tried using RSDLite to flash the original ROM?
[Moto X Q&A] samwathegreat:
It has probably been rooted using an exploit. Be VERY careful or you could lose root forever.

Is the bootloader unlocked? Let me know and I may be able to help you with clear and precise steps.
[Moto X Q&A] NWKENT:
If you erase..are you aware that you will loose Root permanently.?

BUT..If you use the (jcase) RockMyMoto & SlapMyMoto, you can retain Root with these two exploits, Since your device is still on Jelly Bean OS..BUT..to do so, one must be experienced with adb & RSDLite..and you can retain Root over into 4.4_

Sent from my:

Jaocagomez Debloated ROM

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html

"Praise Jah" YOU people.!
[Moto X Q&A] Vebr137:
I did. Its just rebooting and its all.
[Moto X Q&A] Vebr137:
Bootloader is locked. Thanks)
[Moto X Q&A] Vebr137:
Root for this phone is not that important. Im tired that every time I want update a program or install a new one I need to delete google profile from the phone, reboot it and again use google profile. Otherwise nothing is installing.
[Moto X Q&A] samwathegreat:
If root isn't important to you......

BY FAR

, the easiest solution is to follow the instructions in the "Return to Stock" thread - in general subforum, and flash the entire 4.4.2 SBF to your phone. Everything you need is in that thread, including links to drivers, tools, and the SBF files themselves.

Just keep in mind - you'll permanently lose root/wp-off. You can still use the temp-root methods, for now...but once you update to 4.4.4 (it will be pushed out to everyone SOON), you will have ZERO chance at rooting (unless a new exploit comes along, which is extremely unlikely, OR you get your bootloader unlocked through the middleman).

Good Luck!
[Moto X Q&A] Vebr137:
Thnx)
[HTC Tornado] edenc:
Hi, does anyone know of a good source for parts for the Innovation (other than eBay). I have a duff screen and whilst I'm sure it won't be cheap, it has to better than ditching this lovely phone.

Cheers
[HTC Tornado] dm251z:
pocketpctechs has a replacement screen for the tornado (which I think yours is an incarnation), with labor it is $129.

http://www.pocketpctechs.com/main~unit~HTC_Tornado-584~area~repairs~action~updateunit.htm

good luck