yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] schaggo:
Pardon me, a TKP screen...? :confused:

Me too, I though it is hardware or at least a combination of both a hardware design fault and a software bug working together to make the device unusable.
[ONE Original Android Development] pushnoi:
Yeah weird right. Still can't believe it's working. Not sure how it will respond in heat though, shame sun is gone over here.

OnePlus uses different suppliers for it's screens. This fix supposedly only works if you have a TKP screen. You can check using a command @ Terminal:

Source

Edit: Sorry, it's a TPK screen, not TKP... lol
[ONE Original Android Development] glwilliams4:
Just flashed r43 and my touchscreen is responsive like never before. Excellent work! I was strongly considering RMAing, but no need now.
[ONE Original Android Development] oriveradel:
r43? Are you on cm12
[ONE Original Android Development] glwilliams4:
CM12s
[ONE Original Android Development] inzaghi89:
Just created this thread to thank you Franco for awesome job. I've enough of waiting for OP/Cyngn fix for OPO. Still waiting for their reply at support. On each step they want video or photo. I'm glad that this fix my issue and OPO works fine now.

I saw few pages before that there is issue with dailylight. Same here, but I can live without it. It's not big deal with comparing to touchscreen issue ;).
[ONE Original Android Development] DerRomtester:
What is the problem with KCAL? This may help

https://github.com/DerRomtester/one_plus_one/commit/efcf440f7e6c4ca0f672c19395b99ffb5372c8d4
[ONE Original Android Development] madcrow1984:
boot.img file

HII I have downloaded the boot.img file but how can I open it on my OnePlus? What do I need to do to install it.

thanks in advance
[ONE Original Android Development] phoenixita:
Flashify.
[ONE Original Android Development] DerRomtester:
Or use fastboot on your pc.

fastboot flash boot boot.img
[ONE Original Android Development] _ASSASSIN_:
or you can flash it in recovery if you are using the latest TWRP
[ONE Original Android Development] franciscofranco:
I already merged it, made no difference, the bug is still there.
[ONE Original Android Development] emewhort:
Thanks you
[ONE Original Android Development] Vivek_Neel:
+1

I was very annoyed with the ghost touch. Now its no more I guess.

A big relief. Bacon is a beauty when it works fine.

Thank you Franco mate :)
[ONE Original Android Development] jgcaap:
Sorry but I didn't understand. What's the bug?
[ONE Original Android Development] hughfollett:
With KCAL merged in the kernel, sunlight enhancement is broken

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] finistere:
I don't get all this talk about touchscreen problems which are supposed to be solved in r43. Never had these on my OPO.

I do have serious battery life problems with r43 on CM 12 (20150415), though. My OPO is losing about 12-14% battery over night with r43, while it was just 2-3% on r42 and earlier. Same system setup and all.

I did check with CM12.1 (20150515) with stock kernel last night which should have the same touchscreen patches as r43 and I get the same drain of about 12-14%.

That's back to r42 for me. No problems at all.
[ONE Original Android Development] madcrow1984:
Thanks guys, for your quick response. Sorry but I am a real noob on this. :) Do I need to store the file on the phone? I have a mac computer and I found out it is more difficult to install updates.

For example I received an (possible) fix from OnePlus after my complaints. But OnePlus told me the update was only possible from a Windows computer. So I needed the borrow a windows laptop. I have installed the update and nothing changed :( and also it downgraded the phone back to KitKat instead of LolliPop... Luckily the auto update started and after a few updates it was back on Lollipop again but still screen issues...
[ONE Original Android Development] Enea307:
The new r43 boot.img doesn't let my OPO to Boot. Have to flash back my Rom. I have touch problems. Was hoping this .img worked. Now im on euphoria 1.1 03.05.2015
[ONE Original Android Development] DerRomtester:
This kernel does not yet work on cm12.1 based roms.
[ONE Original Android Development] wopch:
Same problem for me, anyone have an idea ? I dont want to return in boot.img stock, I like kernel's Franco :)
[ONE Original Android Development] inzaghi89:
I've same issue. But my screen has been fixed. It looks like that only some screens are affected with this touchscreen issue. But the battery is worst than on stock rom. On stock over the night my battery lose 2-5%. Today I've checked and it lose 15%.

But still I'm glad that screen issue gone.

P. S. can somebody tell me why I'm not able to respond over tapatalk?
[ONE Original Android Development] Hoka-Hey:
look here: http://xdaforums.com/oneplus-one/development/toolkit-mac-os-x-toolkit-unlocking-t2807574

as easy as stealing ice-cream from a baby!
[ONE Original Android Development] phoenixita:
Flash AK.246 man ;) franco doesn't support 5.1.1 yet ;)
[ONE Original Android Development] madcrow1984:
Thanks. I have tried the link but some of the links are "dead" so no tutorial. When I open the Oneplus Mac app I have many options and don't know which option I need to choose. The boot.img is on placed on my desktop. Lets hope OnePLus soon comes with an official update.
[ONE Original Android Development] Astraion:
Idle Battery Drain

Seems like the new touchscreen fix is draining battery in idle mode..

I'm on latest COS12 and I haven't changed anything, I just updated from #42 to #43. The screenshot with lower values is using franco 42. After I flashed the new 43 with the touchscreen fix strange things started to happen: http://imgur.com/a/rgpMn
[ONE Original Android Development] Aka91:
They revert the fix in today's nightly. They say battery drains when idle.

View attachment 3318630
[ONE Original Android Development] machikoko:
phone crashes

I'm running cm12s. After flashing r42 kernel, the screen turns inverted colour. The phone cannot detect the sim card anymore. Then I revert the rom using nandroid. And it restart by it self repeatedly every minute or so. Have this problem since last Saturday. Help me..

.......:(:(:(
[ONE Original Android Development] schaggo:
You better post all of it or a link instead if a screenshot.
[ONE Original Android Development] darshan_dex:
R43

Can anyone provide me the link for r43? I can't find it anywhere..:confused:
[ONE Original Android Development] inzaghi89:
Wow that's really great news. Hope that this update will be available soon at Franco kernel too :good:
[ONE Original Android Development] SimonTS:
http://xdaforums.com/showpost.php?p=60747459&postcount=8989
[ONE Original Android Development] LSiR:
No zips yet all we have now is a boot image

Heres a link

http://xdaforums.com/showpost.php?p=60747459&postcount=8989
[ONE Original Android Development] inzaghi89:
Here is an url for path with battery draining review.cyanogenmod.org/#/c/98677
[ONE Original Android Development] :
Wait, did they just removed touch fix in latest nightly? Why when everything was working fine..?
[ONE Original Android Development] Vivek_Neel:
Because of the battery drain .

Use the search button next time or try to read the last few posts :)http://xdaforums.com/showthread.php?p=60800085

http://xdaforums.com/showthread.php?p=60806995
[ONE Original Android Development] inzaghi89:
Interesting comment at this change: "The extra drain only comes into play when double tap to wake is enabled."

I'll check it on my device now. Hope that this is only issue. Can't back to stock kernel without synaptic firmware update.
[ONE Original Android Development] :
I read it, but i didn't had battery drain, my One was working perfectly for the first time in last 6 months. Now im going back from today's nightly to 15.05.
[ONE Original Android Development] jmudrick:
Terrible drain here even with double tap disabled (1.45%/hr)
[ONE Original Android Development] venky716:
Doesn't seem to matter, drain persists even with dt2w off.

http://xdaforums.com/showthread.php?p=60799931
[ONE Original Android Development] Doo Doo:
Just wondering why flashing from r41 on deletes the (Enable on-screen nav bar) setting under buttons tab
[ONE Original Android Development] schaggo:
It's 30mAh which still is like nothing. We have a 3000mA battery and USB slots everywhere we go. Not worth the trouble of the buggy touchscreen.
[ONE Original Android Development] :
What if it drains 30mA every second your phone is so-called sleeping?
[ONE Original Android Development] neotoky:
The battery drain is real, went back to r42
[ONE Original Android Development] schaggo:
[MENTION=4783640]sprremix[/MENTION] This would empty the battery 36 times per hour. So you'd have to fully recharge your phone from zero to 100 roughly every one and a half minutes. Highly unlikely.
[ONE Original Android Development] inzaghi89:
I confirm that disabling double tap wake up doesn't help. After half day when my phone was idle battery drain still occurs.
[ONE Original Android Development] FloorFox:
Hey i wanna ask is conservative governor more battery friendly than interactive? Or its the other way around
[ONE Original Android Development] schaggo:
Interactive is quite reactful, thus uses quite some battery.

Conservative is batteryfriendly.
[ONE Original Android Development] indesisiv:
It doesn't, I am on r42 and the option is there for me.
[ONE Original Android Development] critofur:
Every 5.1.x ROM I've tried has had problems of one sort or another.

Sadly, I started getting email app FCS once I installed r43, but, touch screen problems are becoming intolerable so I'll have to put 443 back on and just not use the stock email app :(
[ONE Original Android Development] Doo Doo:
Right now I'm on r40 because it doesn't delete the on-screen buttons setting but as soon as I try to flash one of the latest kernels it deletes the setting for some reason I don't understand that
[ONE Original Android Development] LSiR:
R43 compatible with CM12.1/5.1 Roms?

Any other bugs n kinks other than the stock email app?

Heard it can cause a bootloop.
[ONE Original Android Development] Doo Doo:
1st pic is with r40 & the 2nd pic is after flashing r42
[ONE Original Android Development] indesisiv:
Must be something to do with your ROM. I am on stock COS12 and that option is there for everyone else!
[ONE Original Android Development] inzaghi89:
Which ROM are you using. I'm on stock COS12s as [MENTION=2712461]indesisiv[/MENTION] and I've that option on both - R42 and R43.
[ONE Original Android Development] mmurphmsu:
Nope, it's been stated several times.
[ONE Original Android Development] Doo Doo:
I'm using Pacrom & like I said already I'm on r40 which doesn't delete the setting but if I flash r42 or r43 it deletes the setting but as soon as I reflash r40 the setting comes back
[ONE Original Android Development] andrea90:
Could I use r42 on COS12? Thanks
[ONE Original Android Development] inzaghi89:
Yes you can use r42 on COS12s.
[ONE Original Android Development] anjo88:
I have version r43 finally my touch is working fine but my network and battery life decreases a lot and the phone lose networks from time to time anyone with the same problem?
[ONE Original Android Development] SimonTS:
You would be well advised to actually READ the last few pages of a thread before asking such a question. It has been discussed many times.....:eek:
[ONE Original Android Development] anjo88:
the battery drain i read and is real but we have a opo so we need to choose drain ou touch issue I prefer drain :crying::crying: But I like to know if some one has the network problems?
[ONE Original Android Development] Ahmed Shawky:
I actually have the same question is that better than boeffla Kernel for solving the touchscreen issue without network issue
[ONE Original Android Development] inzaghi89:
For you guys which have battery drain issue. I've solved this in some way (few pages back someone wrote about this).

1. Disable doubletap wake up screen;

2. Disable doubletap turn off screen

3. Disable sunlight and color enhancement in screen & light;

4. At the end in privacy guard (settings/privacy) disable for Google Play Service: wake up, keep awake and auto start.

I've charged phone yesterday (unpluged at 3 pm) and now I've 43% of battery. One think which pissed me off is waringn that "Google Play service has stopped".
[ONE Original Android Development] anjo88:
I will try this charge my phone and give my feedback
[ONE Original Android Development] krzee:
ya you had told him to check his inbox to get a copy with diagdriver, but i found a good one already. thank you though
[ONE Original Android Development] anjo88:
I do what you said but my battery life is still crap
[ONE Original Android Development] blahquader:
Same here.

In the CM12.1 official nightly Thread is a link wich pionts to that file: FW_CM12.1_150514_TOUCH.zip.

Is this the same as in the r43 included boot.img?
[ONE Original Android Development] schaggo:
Could be anything. Could be you yourself. Get a proper power statistics audition app (I recommend Better Battery Stats) and learn how to use and read it. This way you'll find the culprit not by randomly tapping around in your OS settings doing this and that.

Hint: by what you said it's probably not even kernel related but some crappy app producing wakelocks. I stand corrected if wrong, of course.

The touch driver is compiled into the kernel. How would flashing a zip file get that driver into the kernel? Kernel is a sealed off image. I'd welcome if you'd elaborate more on what you mean.
[ONE Original Android Development] blahquader:
Sorry dear Mr schaggo. My english isnt perfect.

My question is: There is a touchscreen fix implemented by franco in r43. Dont know if it is a driver or firmware. Just want to know if its the same as mentioned in the other thread, or if there is maybe a new one.
[ONE Original Android Development] anjo88:
Hey man I do all this I don't have wakelocks the problem is on kernel r43 no any app because the network is terrible and all my juice goes away
[ONE Original Android Development] schaggo:
As said in the previous post: touch driver is incorporated into the kernel. It cannot be flashed separately.

If you have a kernel which does not have the updated touch driver in yet, there is no way to get it in. You must find, download and flash a kernel which has it included.

And if you want anyone to have a look what you mean by that zip file, you must link to it. I won't be browsing the ridiculously huge CM thread to find a link to a zip.

These are the relevant commits from CM:

Update of the driver on 14.05.2015: http://review.cyanogenmod.org/#/c/98287/

Reverting the driver on 17.05.2015: http://review.cyanogenmod.org/#/c/98677/

And to feed the trolls a bit: why would you become all hot and sexy on about your English language skills? My native language is Swiss German, I'm not an English speaker at all.

---------- Post added at 15:47 ---------- Previous post was at 15:44 ----------

qcom_bam_dmux (or so, I don't have it ATM) kernel wakelock? Juice doesn't simply "evaporate", if it's consumed, BetterBatteryStats (BBS) will show.
[ONE Original Android Development] anjo88:
Yes but don't you Reed that cm revert the patch on touch because of the battery?
[ONE Original Android Development] schaggo:
What are you trying to tell me? I even linked to the commit from 17.05.2015.
[ONE Original Android Development] HWAM:
Here you go:

https://forums.oneplus.net/threads/new-synaptics-firmware.310743/

http://magnamentis.com/FW_CM12.1_150514_TOUCH.zip

Please tell me if this zip is a touchscreen driver, and how it works if you tell us the driver is part of the boot.img kernel.

I want to know if flashing this zip on Build 05/23 is going to help me. I use 05/15 now (with touchscreen driver in it) and it works perfectly.
[ONE Original Android Development] schaggo:
No, this is no touchscreen driver, it's simply some firmware package probably stripped from a CM12.1 nightly. Again: touchscreen driver is inside the kernel, so it is inside the boot.img and part of the programming, part of the code. You cannot "flash the touchscreen driver". This is not possible. These packages won't do anything touch-related. You must flash a kernel with the respective commits included to get the updated synaptics drivers.

And I don't simply "tell this" to you, thats the way it is. Period. Or would you mind explaining me, how Franco (or any other kernel dev for that matter) "magically" slips the 30+ megabytes large package linked to above into your device with an only 6-7 megabytes large kernel zip or img file?

Yes, the new driver works wonders, without it my device is unusable. Therefore I only run kernels with the new driver included. With it my OnePlus One works as expected.

But as pointed out, flashing this zip won't do anything. It contains no kernel, no nothing, it won't change anything touch related. If you want the new driver, find yourself a kernel which runs with your ROM and contains the driver. There's plenty around.
[ONE Original Android Development] HWAM:
Thanks for explaining me. Luckily you are honest. Do you think synaptics will update their driver on short term again (one without battery drain with dt2w on)? I hope it will be included in CM12.1 again soon?
[ONE Original Android Development] schaggo:
Why would you think I know? I'm a regular consumer, just as you are.

Two further comments (I read your rants in the oneplus forum thread):

Regarding your "fu**ing OPO customer support" blah blah: the new drivers are not ready for prime time. As can be witnessed, they lead to battery drainage and thus are not "stable" or "usable". You as an individual may be brave and test them by flashing highly unstable software, eg. the nightly builds. But they cannot and should not (and in fact are not) be included in a stable release for end-customers. There is no "fu** this sh** this s*cks" blah blah, as effectively there is no "fix". There only is unstable code, which fixes these specific sympthoms but introduces others, so it's clearly not ready yet for the public audience. But they're working on it (and are on the right track) as the current state of affairs shows.

Read the nightlies changelog. There is nothing "new" since 15.05. in regards to nightlies. There is nothing "new" since several weeks, to be fair. There is no need to update to 23.05. build, stay on the 15.05. build if it serves your needs. Personally I went to weekly or bi-weekly updates since features stabilized recently in CM12.1.

One last remark: OnePlus basically has no say at all in this. All software is provided by Cyngn/CyanogenMod, OnePlus is totally dependant on them, being their software provider. So OnePlus customer support can do sh** against your problem.
[ONE Original Android Development] HWAM:
Thanks again..

I appreciate your meaning. We are on the same site. Yes, I'm following the OnePlus posts every minute. You told me more in one post than I heard from OnePlus in more than two weeks. Thanks for the information. I know OnePlus cannot do a thing but they can inform us. Yes, the 05/15 build is fine for me. I just posted a "flat line" battery stat, perfect with "powersave"/300/300 with Tasker with screen Off.

I have a support call at OnePlus but the only thing I must do is take photos and openup the cover. Idiot protocol. Just tell me the truth OnePlus!!

Can you tell me if the new drivers/kernel also use more power when the screen is on? I turned Off all the gestures.

Thanks again.
[ONE Original Android Development] Stroky:
So, i´m using the One completly without any gestures or stuff like this and i´m not notice any drain with that fix included!

My battery lifetime is completly the same as it was before the fix was included!

So go on and test it!
[ONE Original Android Development] schaggo:
They did, Carl Pei informed the userbase that a fix is in the workings. Which is absolutely true as nightly-flashers can testify. But, as pointed out, the fix is unstable and not ready for primetime. It even had to be recalled/reverted.

As said, OnePlus - especially the poor bastards in the customer support department probably earning $2.50 per hour - probably know less than some individuals on these forums. I am also guessing that since they broke up, Cyngn is treating OnePlus with the least possible respect. I could bet my ass that OnePlus became a disturbance for Cyngn and enjoy little to least priority. No money can be made there anymore, it's only hordes of dumb users shouting and flaming the interwebs about uninteresting problems which are hard to fix. Neeext.

So did I. My request was approved, I may RMA my device as soon as I have a replacement at hand to bridge the gap between sending my One and receiving a fixed one back.

I cannot. I'm a heavy user and easily run down my battery over the course of a day. The couple percents the fix may or may not use are totally irrelevant in my use scenario. Thus I cannot comment if enabled or disabled gestures and DT2W have any influence at all. The general consensus seems to be yes, I don't trust what others say though, the number of n00bs is too damn high these days on xda and similar places.

You're forgetting one thing, calling OnePlus names and giving them sh**: let's assume our device would cost twice the cash but suffers the same problems but was made by Samsung, LG or HTC and not by some small chinese startup mainly relying on social media for marketing and customer relations. Would you go on and flame in their forums and expect the "openness" we actually get from OnePlus? OnePlus might act like a bunch of fools and their communication strategy might su** balls, but to be honest, I think it's way better than anything you get from the big boys. HTC's M9 getting throttled to middle-class device-like performance due to heating issues, LG doing the same thing with their Flex-whatever-it-is, Galaxy S6 slowing down to a degree where it's becoming unusable because of ****ty memory management, do you really expect those players to give a sh** about what the customers flame about on the web? No.
[ONE Original Android Development] HWAM:
You want to RMA your device, you think a replacement model is working fine? My device gave problems above 25/30 degrees Celcius. But with 05/15 it's great. I don't know if I want a RMA. All the effort for a same device, maybe with the same problems. I hope they can fix it with a firmware update. Otherwise, my current 05/15 is usable very well. Your device is really bad?? Because you want to RMA it? Is it not working fine with the new drivers?