yashsingh1/xdaforums huggingface dataset:
[ONE General] javideslomao:
Looks very much like it! see comments at: http://review.cyanogenmod.org/#/c/70649/
[ONE General] Vortex1969:
I uploaded the stock CM 11 kernel image I built 3 hours ago with the touchscreen firmware update if anyone wants it.

(Not for stock ROM CM 11S)

http://xdaforums.com/showthread.php?p=54908835
[ONE General] drms12:
I don't know what's improved, I still getting random swipes all over the keyboard. I'm currently using the latest nightly, which has the new firmware built in.
[ONE General] shure2:
I have only been trying it for about 1 hour but I haven't had any problems yet. Even if it turns out to be 50% better than before then it'll be good progress.

I don't think this is the final finished solution though from the notes that I read. I think there is a little bit of an underlying issue with the hardware which they obviously won't say anything about (to do with heat and proximity to other electricals)

Maybe try a clean flash?
[ONE General] drms12:
It's after a clean flash.

Please just try this and tell me the results : open some text panel and write the letters f and h back and forth, quickly. Use a keyboard with swipe option (Mine is SwiftKey).

Tell me what happens.
[ONE General] TheProd:
FYI: I have deactivated all gestures and dt2w -> My ghost touchs are gone (since one day of use).

Maybe a little help till the fix comes.
[ONE General] spacemanvt:
can you give us some details? I would be interested to find out what notes you have.

My nonresponsive touchscreen issue seems to be resolved with the new driver but is still not as good as my old nexus 4
[ONE General] quattrob8:
Touch responsiveness is much better however ghost swipes still appear when typing.
[ONE General] shure2:
If you look a few pages back someone linked to the CM developers part where they submit and assign changes, there one of the developers talked about this not being the absolute final solution but required asap. I'd be surprised if synaptics rushed out a half arsed driver, I suspect this might be the finished article. After all on the the kernel devs said it wasn't just a firmware thing but they couldn't say more. Again I can't be bother to find the post, you'll just have to trail the forums like I do
[ONE General] spacemanvt:
ok i will look around. you think its a hardware issue too?
[ONE General] TheProd:
Finally! Franco R13 with CM Touch Fix + CM11s 30O -> No problems !! :D:D:D
[ONE General] ilea94:
What CM Touch are u talking about ?
[ONE General] Denisuu:
I think he is talking about franco kernel r13 it has a new touchscreen driver in it.
[ONE General] ilea94:
Ahh too bad :(

It didn´t work for me out :(
[ONE General] andresantos:
you can use it with the stock cm11s 30O ROM?
[ONE General] TheProd:
Yes!
[ONE General] Denisuu:
Yea sure :) I have it on rooted stock 30O
[ONE General] stoerebink:
I may sound like a total n00b, wich i am.

But can you please explain here how i get this version on my (not rooted) OnePlus?

This explanation can be VERY helpful, because many, many owners of the OPO suffer from the ghost touches....

Thanks so much!!
[ONE General] Denisuu:
Yea first you will need to unlock your bootloader, there are tools that make it really easy. Then you can flash a custom recovery and then rooted 33R stockrom. Then download flashify from the playstore and franco kernel and flash the kernel. I will post the links here when I'm on a computer.
[ONE General] javideslomao:
See EDIT 5 in my original post. The attached boot.imgs only work on the 25R build and the same patch applied on the latest update (33R) doesn't fix nor alleviate the issue. Don't bother trying.
[ONE General] javideslomao:
BACON-55 sufferers: see OP, I just uploaded a new image with this change in: http://review.cyanogenmod.org/#/c/72720/

See boot-33r-f367c1f.img in the thread attachments. Flash with flashify of fastboot.

About 10 minutes into the new synaptics firmware, ghost swipes are gone. I want to be very cautious about it, but this might be the ultimate fix.
[ONE General] kahtc:
Nope

I have a better typing experience with the new boot image, but the ghost touches are still there :(
[ONE General] javideslomao:
You're right. 10 minutes more into it and swipes are back.

I'm losing my faith.
[ONE General] oscarandjo:
Still has issues with typing for me, I think I can type quicker than before though. With the multi touch tester it screws up near the bottom of the screen...
[ONE General] shure2:
I can type faster than I have been able to before. Screen touches seem to be recognised quicker. I also haven't had any swipes but its only been 20 mins and my phone isn't particularly hot (when I get the most swipes). Will report back.

Also I'd like to mention I don't have the grounding issue like others do
[ONE General] c1-p8:
Thanks! my OPO seems to work perfectly now :good::fingers-crossed:
[ONE General] ecksreturns:
I can also confirm that after r17 and now r18 , typing over stock kernel , has improved by 80%! I do not use the Flow/Swype feature on Swiftkey , but fast typing is really really good now! FINALLY!

Can not wait to try out r19!
[ONE General] LoveMyNewTelephone:
Can I 'sideload' the img via TWRP?

Can I 'sideload' the img via TWRP ?

It seems you need a zip for that.

(don't have a computer available to use ADB)
[ONE General] gerciolisz:
you can flash img through android terminal emulator look for it in this forum.
[ONE General] javideslomao:
You can use flashify to flash imgs without a computer (https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en).

Or just flash franco kernel r18, it also has the latest firmware and there's a zip for it. The one posted here is pure 33R + the firmware.
[ONE General] saikm:
does ak kernel have the latest synaptics firmware?
[ONE General] LoveMyNewTelephone:
Thanks a lot. That worked perfectly.
[ONE General] javideslomao:
Doesn't appear so looking at their github sources.

But you can flash either the latest boot.img from here or franco kernel, then flash AK back. The firmware lives in the synaptics chip. Once it's upgraded, new kernels won't attempt to downgrade it.

To know which firmware version you're on, use any terminal app on android to run this command:

cat /sys/class/input/input0/baseline_test

You should see something like:

trx-to-trx raw readback: 0 0 0 0 0 0
imageid=0x14001219,deviceid=0x140012[COLOR="Red"][B]19[/B][/COLOR]
0 error(s). All test passed.

19 in red is the firmware version, latest is 19.
[ONE General] saikm:
thank you very much!
[ONE General] ilea94:
too bad your latest Kernel doesn´t boot with official MIUI.

There´s something wrong with MIUI :D

Can u maybe tell me how to modify this Kernel with the latest Synapse patch ?
[ONE General] jlevy73:
Typing has definitely improved with the new firmware. What has not improved (for me at least) is swiping between home screens or in the app drawer. Swipes still register as touches and touches as swipes.

---------- Post added at 06:57 AM ---------- Previous post was at 06:42 AM ----------

Actually that's not true. I flashed the boot.img in the OP then flashed AK and it downgraded the firmware to 1217.
[ONE General] saikm:
yes...me too :(
[ONE General] javideslomao:
You guys are right. Looking at the kernel sources more closely, the firmware's configarea (where the latest changes have happened) is flashed when versions simply differ, even if the one in the chip is newer.

So, nevermind... Stick to OP's boot.img or franco for now.
[ONE General] edgarf28:
Edit:

-- Nvm, didn't understand it correctly. - -
[ONE General] jlevy73:
It's all good...thanks for posting the modified kernel though.
[ONE General] javideslomao:
Interesting finding...

Just tried the "fhfhfh" key bashing test on a GNex and a Galaxy S3 and, much to my surprise I get crazy ghost lines just like on the OPO.

Also, both the GNex and the S3 do terribly bad in the two converging lines test some people posted elsewhere.

There are lingering issues like the erratic multitouch when ungrounded, but ghost swipes wise the last firmware is a satisfactory fix for me considering the "fhfhfh" problem is likely a technology limitation of current touchpanels.
[ONE General] jlevy73:
Those are both older devices so I just tried it on my N5 and M8 and both give perfect results when key bashing. I think this might be a technology limitation of the OPO :)

The other thing of note is that I have played with my friends OPO and his was perfect, no touchscreen problems whatsoever. So while I do hope a software fix can improve this issue I believe part of it might of this problem lie in the hardware. Don't have empirical proof just a theory.
[ONE General] fix85:
I've tried to run your command to see my firmware version, is it normal that I have errors inside the report?

/input0/baseline_test <

1++ raw_cap[05][04]=1773 is not in range[0949~1762].

2++ raw_cap[05][05]=1760 is not in range[0946~1757].

3++ raw_cap[05][06]=1759 is not in range[0942~1749].

4++ raw_cap[06][04]=1811 is not in range[0950~1764].

5++ raw_cap[06][05]=1760 is not in range[0947~1758].

6++ raw_cap[07][04]=1904 is not in range[0957~1776].

7++ raw_cap[07][05]=1765 is not in range[0944~1753].

8++ raw_cap[08][04]=1885 is not in range[0948~1761].

9++ raw_cap[08][05]=1774 is not in range[0954~1771].

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

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

imageid=0x14001219,deviceid=0x14001219

10 error(s).

u0_a125@A0001:/ $

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] jgcaap:
Got that one.
[ONE General] javideslomao:
Mine have those too, occasionally. If you run it again you might get 0 errors. No idea what they mean, they are supposed to be the digitizer cell capacitances at rest and they should be within the [x~y] ranges according to the test. I try not to get too OCD about that... The touchscreen just works with firmware 19 and that's what I care about.
[ONE General] fix85:
Tried multiple times but I always ended up with errors.

Yeah with firmware 19 things are definitely better but I still get unwanted swipes when typing.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] mdavario4:
Just got this mail from Oneplus Support:

"This issue seems to be a known problem we've identified as a software issue, and after strenuous testing and development work, we're confident that the next major software update (due in a couple of weeks) will resolve it. As this affects all devices with certain software setups, I'd like to advise you to wait for the update."
[ONE General] LoveMyNewTelephone:
So SAD

So SAD:

I have the new firmware (r19) and it looked promising, BUT I just got a very big ghost-swipe.. I tapped the z (bottom left) then the i (upper right) with the same finger (so there is ample time between them), and I saw a big swipe from the z to the i (using Swiftkey).

In addition, I have to say that the screen still doesn't pick up on taps every time..

I did the grounding-pillow-test as well, and it failed miserably.

I'm kind of loosing faith here. I really think it is a hardware issue and if that is the case, I will be buying another phone.

I regret having recommended this phone to all of my friends. At least 8 people have bought this phone on my recommendations

Production date (July), don't think this is of much use though. I've seen 1+1's that are just new and they too have the issue..
[ONE General] jon-:
It's ok, synaptics are new to the touch screen market, it's not surprising it's going to take over 3 months and numerous firmware updates to try and fix a simple "software" problem.

Oh wait :(
[ONE General] Denisuu:
I'm sorry to hear this.

I am making a list with people that have the problem and the manufacturing date.

I used buyers protection to get my money back. I also recommended the phone to a lot of friends. They are all very happy with it. Still a few also have the problem.
[ONE General] anmar21:
Latest cm11 nightly and AK have resolved the issue for me.
[ONE General] Krunk83:
I'm having these issues as well.

Sent from The One+ One
[ONE General] saikm:
due in a couple of weeks.....

we can say good-bye to 36R
[ONE General] jlevy73:
Just received this from One Plus support:

"Thank you for contacting us, I apologize for the inconvenience caused to you. Well Yes this is still a software bug for many people. Since you have already updated the software so there is one last thing that I would request you to perform, this will clear out the cache files of the older firmware.

Steps for hard reset.

1. Back up all your important files and information, as the process will erase all data

2. Shut down the phone, and turn it back on while holding the Volume Down button until you feel it vibrate

3. Once in Simple Recovery, select "wipe cache partition" and swipe to the right or press the power button

4. When you get the "Cache wipe complete" message, continue and select "wipe data / factory reset" to fully reinitialize your ROM

Let me know if the problem persists after these steps!"
[ONE General] Krunk83:
I got this too.

Sent from The One+ One
[ONE General] jon-:
They've been sending that out since before 30.

Unsurprisingly it doesn't fix anything, as it's a HARDWARE ISSUE.
[ONE General] gerciolisz:
It may not be hardware issue but still their drivers can be bad. But we still dont know that
[ONE General] SuRPasser:
Hello guys, after 1,5 month using the opo, this ghost swipe issue becomes really annoying. This is my video in YAMTT paiting mode.

https://www.dropbox.com/s/9qfaf1rmb029s57/SCR_20141002_234906.mp4?dl=0

On the video it is can be clearly seen the multiple ghost swipes towards each other. Im am confidently tapping to the same position, but the screen driver or smth else (i mean hardware problem) constantly doing these swipes.

Rom: liquidsmooth latest plus ak 50 kernel. Ive tried different roms and thd issue always appears, so i tend to that is real hardware proble or may be i still hope the software driver bug that hasnt already been found.
[ONE General] javideslomao:
Franco kernel and the "boot-33r-synfw-19.img" kernel from the original post will improve things a whole lot, but not 100%. I still get some swipes but I can type without wanting to smash the phone against the floor. BACON-55 is not marked as resolved yet, so let's hope there will be more synaptics upgrades in the future.
[ONE General] SuRPasser:
hope too... have to say, sometimes (more often recently) the problem disappears! I usually open YAMTT paint tester, and see no ghost swipes at all, or several swipes and then they are disappear... So i still dont know either this is software issue or hardware.
[ONE General] Overdose1986:
OMG stock 33R with updated firmware? Amazing
[ONE General] Jole7:
What about the newest touch firmware?? Is working great for me!
[ONE General] Theshawty:
Not for me, sadly.
[ONE General] AcmE85:
There will be another one today

http://review.cyanogenmod.org/#/c/75850/

also this was merged

http://review.cyanogenmod.org/#/c/75847/

I don't know what this is for though
[ONE General] fix85:
Suprinsigly enough the 28th nightly touch firmware actually fixed those horribles ghost swipes for me, I can reactivate flow in SwiftKey without any problems.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] linezero:
and then there is a another touchscreen firmware update ahead to be included in the next cm nightly ;)
[ONE General] fix85:
Yep, I'm eager to test it ?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE General] effry:
Anyone have compiled an updated kernel with the new touch firmware? I'd like to test it
[ONE General] Theshawty:
I wonder if it'll fix the crappy multitouch.
[ONE General] thantos:
I actually found the recent update made mine worse than the previous firmware... Hopefully the newer one will rectify this issue..
[ONE General] AcmE85:
AK Kernel has it implemented both for the cm nightlies and cm11s.

Though all my previous issues have been fixed with one of the first firmware updates around september,

today's update feels more snappy in terms of responsiveness.
[ONE General] fix85:
Running FK r30 with the latest touch firmware, now the touchscreen behaves almost like my nexus 5, nearly perfect :good:
[ONE General] Theshawty:
The touch is still junk for me. I can't tell just yet whether ghost touches are gone or not, but the multitouch is still junk.

I suspect this to be a hardware bug.
[ONE General] javideslomao:
Franco Kernel r30 already has this, if anyone wants to try it.

On stock 38R I was having these problems:

Pinch-to-zoom going nuts: very occasional problem, it only happened to me once since the 38R upgrade but BACON-55 comments are full of reports on this. Rebooting would restore it back to normal. Time will tell if today's firmware permanently fixes this. Seeing the commit's diff, only a couple of bytes changed in the configuration area, which means they are somehow finetuning parameters. There are no code changes whatsoever, so I'm not holding my breath on the crazy zoom thing being fixed just yet.

Ghost swipes: I have to admit 38R fixed this 99.9% for me but I still got some random swipes on 38R, especially when quickly typing two keys that are very close together (eg. f-h, u-o, etc.), and much more rarely, between keys that are far apart like 'a' and 'p'. My particular 'f-h-f-h-f-h-f-h' mashing test actually works better on today's firmware, as I can't get any ghost swipe but I still see strange behaviors like an 'f' showing up as a 'd', as if the registered touchpoint were a few millimiters off of where I actually touched. On YAMTT you can see that the blue and red dots do not always appear exactly where you touch when you tap the screen with two alternating fingers quickly. Also, for some people 38R didn't make a difference at all. Maybe the new firmware works better for them.

Bad multitouch when ungrounded: I don't think this will ever be fixed.

That fixes a bug that resulted in a kernel panic when trying to reflash the TS firmware through the /sys filesystem. Totally unrelated to BACON-55 or the TS behavior whatsoever.
[ONE General] zoah:
ghost swpes and unresponsive screen

so, to fix this issue i have to change kernel?

cuz my phone is useless right now. i cant type. my screen is sometimes unresponsive, i have to reboot to make this thing work. but ghost touches still there.

how am i suppose to fix this? can someone clarify this for me please?
[ONE General] mdavario4:
I recommend to RMA your device.... it takes long(for me almost 3 month), but finally I got a new one which doesn't have any touch issues at all. If it is not too late and you did pay via paypal you could also use paypal buyers protection/insurance.
[ONE General] zoah:
I reuqested an RMA. but i still didnt get an answer to that. this is my second Oneplus which is going to RMA.

Im done with oneplus. . as you said, i already did that part with paypal. i asked declaration, and if Oneplus doesnt say anything before 15 december i will receive my money.

What bothers me is that opo is giving people defect phones. that pisses me off.

thanks for your feedback.
[ONE General] XmechaniX:
RMA might be an option but this doesn´t fix the issue. I got my phone replaced and the new one has exactly the same problem. The new phone doesn´t have the cyanogenmod logo on the back. Replacement was fast though.
[Xperia Z1 Q&A, Help & Troubleshooting] ruggyboss:
Time ago I rooted with towelroot (.108, C6903). I totally forgot to get some information about the ta partition. How can I check it? If it's gone, what did I lose?
[Xperia Z1 Q&A, Help & Troubleshooting] danw_oz:
*#*#7378423#*#* from your phone dialer, go to service tests, then security, if there are entries in there and show the status of ok then you don't need to worry, you haven't lost your ta partition. What I would suggest is that you then go ahead to the thread about backing up the TA Partition and do it.
[Xperia Z1 Q&A, Help & Troubleshooting] hush66:
Simple rooting via Towelroot does not remove TA partition. It's unlocking your bootloader that will remove the TA partition. So if you have not unlocked the bootloader, then your TA partition is still there.
[Xperia Z1 Q&A, Help & Troubleshooting] smart8bits:
you can find a useful tutorial of using "flash tool" and how flashing .ftf files, here:

[25NOV][FLASHTOOL GUIDE] HOW TO for n00bies - G-FACE GUIDE

and here is prerooted and deodexed flashable 14.4.A.0.108 :

[STOCK][C69XX][4.4.4] Update to 14.4.A.0.108 [Root & XZDR][DE-/ODEX]

and I highly recommend you to read this very useful post by Great DOOMLORD :

[Xperia Z1][INFO][REF] All the info you need before you begin
[Xperia Z1 Q&A, Help & Troubleshooting] joecool666:
hi, can anyone tell me if there DTCP-IP, is SRM validation [unavailable] [unknown error] can someone please inlighten me on what this mean's, many thanks,joe
[Xperia Z1 Q&A, Help & Troubleshooting] ruggyboss:
Thanks for the answers guys! <3
[Xperia Z1 Q&A, Help & Troubleshooting] ruggyboss:
Good point.. I was wondering this in this very moment, same error
[Xperia Z1 Q&A, Help & Troubleshooting] joecool666:
yeah i called sony about this , and they told me its nothing to worry about, but talking to sony is like talking to a brick wall, but i will call the again cause the lady i was talking did'ent know what the heck i was talking about, bless her , but i will update ya after i call them ,regards joe
[Xperia Z1 Q&A, Help & Troubleshooting] Afterlife737:
Hi ! I am a new Xperia Z1 owner and want to root, unlock the bootloader and install a custom recovery so I can flash roms. I am on the new .108 firmware - any guides ? How do I do this ? Thanks for your reply in advance !
[Xperia Z1 Q&A, Help & Troubleshooting] ruggyboss:
There's a thread that should explain everything you asked.. For root and custom recovery there's a really simple trick with towelroot (look for it), for everything else you should look here: http://xdaforums.com/showthread.php?t=2439328
[Xperia Z1 Q&A, Help & Troubleshooting] Afterlife737:
I've read it through already but it's for older firmware so I can't follow it... Is an option to root the Z1 whilst having the bootloader locked then backup Ta partition and then unlock the bootloader and install a custom recovery?
[Xperia Z1 Q&A, Help & Troubleshooting] ruggyboss:
Look, you're right saying that's an old thread but you should just download the latest corresponding files (http://nut.xperia-files.com) and you should be done! Otherway Google "how to unlock bootloader xz1" or stuff you need and you'll find more recent guides.
[Upgrading, Modifying and Unlocking] loko34:
Farkındayım belki bu konu için başlık açmam kurallara aykırı ancak çok acemiyim ve burada yazılanların çoğu İngilizce..Ama çok acil yardıma ihtiyacım var..İlgilenen olursa hayır duamı alır..Çok yeni yurt dışından Qtek 9100 model cihaz satın aldım..Ancak okuyorum ve görüyorum ki ROM yükseltme olayı var mış ancak benim cihazın CID kilidi açık mı kapalı mı onu bile bilmiyorum ..Cihazımın özellikleri şunlar..:

Mate Qtek 9100 ( K-Jam)

Model No:WIZA200

Rom Version : 2.17.7.2 WWE

Radio Version : 02.07.10

Protocol Version : 413.1.03

ExtROM Version : 2.17.7.102

CPU : OMAP850

EegleTEC MiniSD : 1 GB.

IPL : 2.17.0001

SPL : 2.17.0001

GSM : 02.07.10

OS : 2.17.7.2

Bu cihaza nasıl ROM yüklerim..? Birde İMEİ değiştirme işlemi hangi durumlarda ve nasıl yapılıyor..?Türkçe açıklamalı bir link versenizde yeter ama lütfen yardımcı olun..
[Upgrading, Modifying and Unlocking] enkidu:
bu cihazın İMEİ değiştiremezsin,çünki G4 chip seti var içinde..

hemen kayıt ettirmeye çalış,yoksa elinde sadece cep bilgisayarı olarak dolaştırmak zorunda kalırsın.
[Upgrading, Modifying and Unlocking] loko34:
peki üstadım ROM'unu nasıl daha hızlı bir hale getirebiliriz..BU konu hakkında yardımcı olabilir misin..?
[Upgrading, Modifying and Unlocking] enkidu:
forumda G4 chip diye arattırma yap.

G4 chip setli cihazlar için verilen ROM linklerini görürsün.

AKU 3.20 ROM vardı en son,G4 chip setli cihazlar için.
[Upgrading, Modifying and Unlocking] loko34:
Üstadım dediğini yaptım ve indirdim aslında sorun indirmek değil ben genel anlamda bunları PPC'yi öldürmeden nasıl yüklerim onu bilmiyorum..Cihaz verilerimi zaten yukarda yazdım ama bu indirdiklerimden hangisi benim cihaz için uyumlu veya nerden başlarım onu bilmiyorum..Lütfen şayet vaktin varsa bana yardım edermisin..?