yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Formhault:
I see. Thanks!

I've also got a JDI panel. Wondering what the other two could be...
[ONE Original Android Development] sathish804:
Mine is also JDI panel, Until now its good.. Will post the results here very soon!!
[ONE Original Android Development] Roulianooo:
Another method to know panel manufacturer (found on oneplus forums)

On a terminal app or an adb shell, do:

Code:

cat /sys/class/input/input0/vendor_id

TP vendor codes being:

Code:

#define TP_VENDOR_WINTEK 1 //Ê¤»ª

#define TP_VENDOR_TPK 2 //TPK

#define TP_VENDOR_TRULY 3 //ÐÅÀû

#define TP_VENDOR_YOUNGFAST 4 //Ñó»ª
[ONE Original Android Development] andip71:
Cool info, mate.

This saves me from hook into the panel driver. So now I can allow to display the panel version in the app in a next release !!!

Cheers

Andi
[ONE Original Android Development] Roulianooo:
BTW touchscreen is buggy on my phone unless i use the draining battery new touchscreen driver :)

dmesg | grep -i panel tells me JDI 1080p

cat /sys/class/input/input0/vendor_id tells me 2 (TPK vendor)

Will test your last kernel tonight :) (need my phone until tonight ;) )
[ONE Original Android Development] Clark789:
JDI panel in my OPO as well...

Cheers

Clark
[ONE Original Android Development] lucap00:
with dmesg it results I have jdi

with cat it results i have wintek

i'm gonna flash test kernel in 30 min
[ONE Original Android Development] rahulrai:
How to check which panel I have?
[ONE Original Android Development] Mentalmuso:
My panel is a Wintek.. I did replace my touch screen and LCD, I was getting massive touch failure on my old screen which I still have in a drawer somewhere. Since replacing I haven't had any touch problems
[ONE Original Android Development] Roulianooo:
Users with touch failures have generally a TPK panel from what i see :)
[ONE Original Android Development] ZaneZam:
Yes and they are definitely fixed for me with a TPK panel, huge difference! I even had a wow effect :) the question is if the new firmware still produces also a huge difference in energy consumption ;) let's see..
[ONE Original Android Development] Mentalmuso:
Does anyone know if I can tell the brand of my broken touchscreen, that I replaced? Via a label or something? I'd be interested to see what brand that was. It was diabolical
[ONE Original Android Development] fmc000:
dmesg ->JDI

vendor_id -> TPK
[ONE Original Android Development] Roulianooo:
You mean with the new driver ?
[ONE Original Android Development] Formhault:
It seems I have a TPK, as well. But the dmesg command says JDI... and something something Oppo (huh).

JDI stands for Japan Display Inc. That's a manufacturer, right? How come I also get TPK reading? [emoji23]

I only had the multi-touch on same x-axis issue... But on the first few days since the issue emerged, the screen was possessed! It "laid down" eventually to just the x-axis thingie...
[ONE Original Android Development] magnamentis:
best over night and check percentage over night. if there is a drain the difference will be significant as to 10% instead of 2% for example
[ONE Original Android Development] Roulianooo:
Ok i just can't resist and flashed the test kernel for CM12.1 just now.

Touchscreen is perfect , no ghost touches :D

Will report back later for the battery drain
[ONE Original Android Development] nk57xx:
Will you offer a CM11S Version with that fix?
[ONE Original Android Development] tsimitsangaz:
Hello guys any info about buying a proper pannel without issues?
[ONE Original Android Development] jukiewalsh:
New to boeffla here so sorry if there's a separate thread for the app but how do I turn on dt2w with the config app? All that I see under the display settings or anywhere else is swipe to wake/sleep
[ONE Original Android Development] andip71:
Please note, this is a completely experimental and unofficial fix. It is not even contained in any CM kernel!!

So, I would only include it if:

- it turns out the fix helps + does not drain battery anymore

- CM also officially puts it into CM12.1

Double touch 2 wake is a basic function of every OnePlus rom. So why should I make it configurable in the Kernel app additionally?

Switch it on in display settings of your rom. Done.

Andi
[ONE Original Android Development] Hilmesh:
JDI here too
[ONE Original Android Development] jukiewalsh:
Good point, I didn't even think about it since I've been always just using synapse... Facepalm

Thanks
[ONE Original Android Development] andip71:
Oh dear... means you are coming from another custom kernel.

Please do not forget to clean up everything left from the previous kernel. Synapse, UKM, init.d scripts, apps etc.

Otherwise everything can happen :(

Andi
[ONE Original Android Development] Mentalmuso:
I've had one random reboot about a minute after flashing, but the test kernel had been running solid since. About an hour
[ONE Original Android Development] andip71:
Whatever this was, for sure not related to the touch drivers.

Well... 99,9% sure :) (let's leave some rest probability)

Andi
[ONE Original Android Development] jukiewalsh:
Yeah I know I'm not that bad :silly:
[ONE Original Android Development] Mentalmuso:
There is no real reliable way to tell if a replacement panel will be better than the one you had. But you have to believe of there are different manufacturers out there that some of their processes may affect the quality of the panel. I bought mine off Alibaba. I'll find the link to the seller later if you like, I've had my replacement screen on my phone for a month now and it's going great. I'm not careful with it either, it gets direct sunlight, I keep it in my hot pocket a lot, and I live in hot Texas. I work on pool equipment so it even gets damp a lot

---------- Post added at 11:18 AM ---------- Previous post was at 11:15 AM ----------

Sorry, just realized this is kinda off topic
[ONE Original Android Development] Formhault:
Have you tried the latest experimental build? That should fix your touchscreen issues...
[ONE Original Android Development] schmitzekater:
Oh boy, that experimental build feels so good. ??
[ONE Original Android Development] TorchaOne:
Yes, even if I never had any major touchscreen problems, that I noticed, other than I cant write :) Anyway, first 2 hours 0.5%/h, so for me same normal drain as cm11.
[ONE Original Android Development] pinoymutt:
Just loaded the experimental version here as well, and so far, so good -- but will keep an eye on battery drain.
[ONE Original Android Development] magnamentis:
why should you resist, after all this is the work of [MENTION=947981]Lord Boeffla[/MENTION], no reason to believe it would cause trouble LOL

EDIT: ok since i already wrote this OT i can as well confirm that i just came back from a 3 hours bike ride which means navi, bt-media, and other apps permanently at work and no issues at all, no RRs, no glitches, just the usual perfection less extra drain. FINALLY !
[ONE Original Android Development] Clark789:
My OPO (CM12S) runs since 6 hours with the experimental kernel and no issues so far. No glitches and no FCs. Runs perfect.

The battery consumption is quite normal: i started with 85% battery level and now it has 72%. But i did different calls and i read a while in the internet.....

For the time being no reason to complain!

And the responsiveness of the display is a LOT better!!

I like the experimental kernel very much! Abolutely recommendable!!!

Cheers

Clark
[ONE Original Android Development] Galactus:
Just so everyone knows, we all have JDI displays. The OnePlus One only has a display created by JDI (Japan Display inc) and is a merger between Hitachi, Toshiba and Sony. The difference is they are manufactured by different supplier's. The correct way to check your display panel is this:

in terminal input the following, or navigate to this location and open the file using ES File Explorer as Text

cat/sys/class/input/input0/vendor_id

The different display types are:

WINTEK 1

TPK 2

TRULY 3

YOUNGFAST 4

TPK is most frequently associated with the touchscreen issue
[ONE Original Android Development] gqukyo:
I must be lucky then cuz I have tpk but never any touch issues though watch me get issues now... Lol
[ONE Original Android Development] GForceXIII:
Same here.
[ONE Original Android Development] andip71:
Good morning guys.

All on the experimental version... What do you think about battery consumption so far?

I cannot judge as my router decided to go crazy last night, forcing me on an edge mobile connection. Grrrr.

So no clue how idle battery drain is like...

Anyone?

Andi
[ONE Original Android Development] denyo81:
Good Morning Andy.

After one day with the new experimental Kernel. I think it's the same touch feeling as the workaround beta7. Same battery drain with the old touchscreen drivers. When dt2w is enabled. The kernel beta7 (touch workaround) works a little bit smoother I think.

I'm testing the experimental Kernel for oxygen os.

And thanks for your hard work again.

Greetz Daniel ?
[ONE Original Android Development] Clark789:
Good morning Andi,

BBS tells me 1,7%/h since flashing yesterday. This is quite indifferent for my usage. So, the experimental kernel works very good for me. Very good responsiveness and no exorbitant battery drain...

Have a nice weekend!

Clark
[ONE Original Android Development] TorchaOne:
For me it started promising, 0.5%/h first two hours but at the morning it was 1.5%/h. It's way better than the first try to fix. Had dttw and gestures on all night.
[ONE Original Android Development] sathish804:
I observed a strange issue with test kernel. I have charged the battery to 100% and used it normally in my living room where the temperature is ambient and battery dropped 6% in 2 hours. I went to sleep at 11. 30, I kept my phone near window where temperature is a bit cold and when i woke up in the morning I see a drop of 20% in battery.
[ONE Original Android Development] magnamentis:
- last 9 months generally 2-3% in 8-10h idle overnight

- earlier touch patch around 20% in 8-10h idle overnight

- this version 5% in 10h over one night, could get a bit better because rom and kernel were updated yesterday and often things are getting

another tick better after 1-2 nights.
[ONE Original Android Development] lucap00:
Generally when I arrive at home from school I have 75-80% with about 1 hour of screen.

Now I have 65%

With old corrected driver it was certainly worse than now

I have a wintek panel
[ONE Original Android Development] andip71:
So far the results seem to be:

- touch screen behaviour fixed

- battery consumption slightly higher (if at all) compared to previous fix, that has been reverted back by CM

Good thing, let's monitor the situation one more day, then will decide on Monday whether it will go into official Boeffla-Kernel versions.

Funny is, there is not yet a single comment on Gerrit on that new touchscreen firmware.

Andi
[ONE Original Android Development] tsimitsangaz:
slimsaber support?
[ONE Original Android Development] andip71:
No.

Would require to provide a completely different kernel again. Not planning to add another kernel to my portfolio.

But I know a XDA user here is working on an unofficial port of my kernelf or Slim.

Andi
[ONE Original Android Development] Nagasaky2x:
I've had around 10% of battery drain tonight, around 8 hours of almost full standby (no data, no WiFi, just like a classic "dumb phone"). ZZMove Battery Yank + ZZMove Native Hotplug, -50mV UV.
[ONE Original Android Development] andip71:
Which kernel version exactly? And how does it compare to previous?

Andi
[ONE Original Android Development] Nagasaky2x:
4.0-beta17-bacon-touch-workaround.

I don't actually remember the % with the previous stock kernel I was using, I have installed the 4.0-beta17 (no touch workaround) and will be back tomorrow to compare, so I can compare with the same values (same kernel and config, just changing the touch workaround)
[ONE Original Android Development] Spider-Vice:
The battery here with the new touch firmware seems much better than with the previous touch fix. I didn't have any night drain, but I don't have dt2w activated...
[ONE Original Android Development] pinoymutt:
So far battery life seems comparable to without the touchscreen fix, but I don't have any hard data unfortunately, just "perceived" user experience.

But so far the experimental version on COS 12 seems to be a winner.

Sent from my OnePlus One
[ONE Original Android Development] TorchaOne:
This should be 2 days. Sleep was disturbed early night and did not sleep well anymore. Can't say its tc but now back to beta17 no tc ;)

Edit: no-tc kernel took 1.3%/h. So tiny amount less and is within error marginal.

The question is what is draining.. There is stock kernel by tiny from which he reverted some wake and alarm commits.
[ONE Original Android Development] Spider-Vice:
My battery life also seems just like before the touch screen fix with the new one, which is amazing. :) No sleep disturbances, the phone slept like a baby all night.
[ONE Original Android Development] SABman12:
Can you please (Please please please) post new kernel version for CM11S with the new touch fix that doesnt affect much on the battery life? PLEASE mate

The last one for CM11S with touch fix(version 2.8) eating my battery non-stop, and the one without fix(2.9) doesn't but there are touch problems...

So please it would be just wondeful if you could develop new kernel also for CM11S means kitkat(and not just for CM12S/CM12.1/lolipop).

THANKS!
[ONE Original Android Development] andip71:
Why don't you consider upgrading to lollipop?

Andi
[ONE Original Android Development] SABman12:
I did that more that more that once, tried cm12.1, cm12s, blisspop.. But I just HATE lolipop.

bad battery life at least comparing to kitkat, the brightness auto adjust of the screnn doesn't work so well.

44S was just perfect for me but the touch problems destroy everything!
[ONE Original Android Development] eak1080:
+1 for the cm11s version. There are tons of users who aren't updating to lollipop due to mobile radio/GPS issues. 11s is stable aside for touchscreen issues.
[ONE Original Android Development] andip71:
I will consider it when cm team officially merge the fix into cm12.1 as well + when there is more feedback about battery consumption still.

Andi
[ONE Original Android Development] magnamentis:
that's locial because that's the version with the drain ( old workaround ) which the lord was so friendly to make available to those who prefer proper touch experience over battery, for whatever reason. what i don't understand is that why you don't follow the thread. there have been so many posts on that topic that this should have been clear and if it's clear it's not worth to mention. with 10% in 8h you are even one of the luckier guys, others had around 20% in 10h :) so just update and all is well :)
[ONE Original Android Development] Nagasaky2x:
Thought the one I used was the one with that new shiny firmware detection. I've read around 100 posts back. I haven't used this kernel since kk. As a human I make mistakes and its easy here when such an amount of things get mixed.
[ONE Original Android Development] [armitage]:
Idle drain with the experimental kernel over night(phone in airplane mode). Looks pretty good to me. Let's see how many hours sot I get today.
[ONE Original Android Development] maxver0:
Lastest boeffla kernel with new firmware along with cm12.1 1405 on 2g
[ONE Original Android Development] spavian:
The battery drain with the new touchscreen driver seems normal for me.
[ONE Original Android Development] Nagasaky2x:
beta17-touchtest-1

As far as I can see, the idle drain is much lower than the one I used before. The issue here is that I had Titanium doing a backup programmed for sundays, even that way, my overnight drain was lower. 7% overnight with Titanium working. Seems good to me.
[ONE Original Android Development] Stroky:
For me everything works like a charm as usual!

I never had touchscreen problems and always disabled all gestures and stuff like that.

So it is smooth and sleeps like a baby!

Thanks a lot for that.
[ONE Original Android Development] SABman12:
Thanks alot mate
[ONE Original Android Development] magnamentis:
of course, in one or another form it happens to all of us, hope things go well now. enjoy :highfive:
[ONE Original Android Development] fmc000:
Another positive feedback WRT the battery drain: all is fine with D2TW enabled.
[ONE Original Android Development] andip71:
Then... Looks like I should include it into the new official betas tomorrow? What do you all think?

Could also try to backport it to (another) last final cm11s version...

Hmmmmm...

Andi
[ONE Original Android Development] Stroky:
I think thats an good idea!

Let´s see when cm is finished with their version?!
[ONE Original Android Development] Clark789:
I would highly recommend it... For me it's a step forward! And battery usage is quite normal.

Have a nice day!

Clark
[ONE Original Android Development] marhensa:
we cant use SSH Tunnel + Proxydroid properly in Lollipop :(

we need CM11S kernel with latest touchfix (without battery drain)
[ONE Original Android Development] fmc000:
FWIW, it gets my vote. I tested the firmware playing a touch-intensive game these days and it seems to work perfectly. I was very satisfied with the touch behavior with the current CM12.1 firmware but this is definitely a step ahead IMHO.
[ONE Original Android Development] suaverc118:
Not sure if I should blame Google or kernel... Latest Bliss with your test kernel. Turned data off, closed apps,changed kernel settings to drain less and went to bed and saw this when I woke up. Oh and Google has keep awake and awake toggles off. Look at the awake time under the pic being all white. What kept it up?
[ONE Original Android Development] andip71:
Blame Google then, or the rom you are using.

Kernel has no influence on app wake locks.

Andi
[ONE Original Android Development] nicolahaye:
Can I flash latest beta test on euphoria ? Even though the ROM build is from may 3rd ? :)
[ONE Original Android Development] andip71:
No. See change log to find last version working for you.

Andi
[ONE Original Android Development] nicolahaye:
Thx :) then I already have the latest compatible :)
[ONE Original Android Development] magnamentis:
[MENTION=4551715]suaverc118[/MENTION]

hehe... http://xdaforums.com/showpost.php?p=61078785&postcount=18638
[ONE Original Android Development] suaverc118:
What ROM are you on again?
[ONE Original Android Development] magnamentis:
- blisspop 3.4 ( daily driver )

- resurrection remix 5.4.5

- cm12.1

you're welcom, nice sunday though :) :cool:
[ONE Original Android Development] Maelstr0m:
0.5%/hour battery drain on latest temasek and touchtest, nice!
[ONE Original Android Development] davebugyi:
Same config, same drain with D2TW enabled.
[ONE Original Android Development] Fevves:
I sure would appreciate the cm11s getting the improved display thingy, just don't stop at it if CM team produces their final commit afterwards ;) GG and N1 Boeffla.

Just to motivate it for a bit: I like out of the box cm11s with one particular theme and KK is doing so well, so after switching forth and back I decided to stay on it... call me teh mastodont or w/e, but I simply prefer features over hype ;) Not at you man, just spouting out my voice re cm11s and the need to have the display working as it should *SGS4 had a much better touch response and even though all of them are "lazy" displays, One+1 has an even better touch if using the fix IMHO (almost like a glove mode on some other phones) - using 2.8 final on cm11s without gestures nor dt2w ATM with no virtual drain when idle or asleep :D
[ONE Original Android Development] suaverc118:
I'm on bliss and it drains with latest test kernel. 3.5 hours SOT. Never have I had this type of battery. Maybe I should go back to Tam.
[ONE Original Android Development] SABman12:
Sound awesome! Looking for the Cm11S new final kernel! :good:
[ONE Original Android Development] suaverc118:
No issues with Google app?
[ONE Original Android Development] gondsman:
Yeah, I'd say the latest test kernel doesn't show much drain at all...
[ONE Original Android Development] Roulianooo:
Latest test kernel has been rock solid for me during the week-end, no massive drain (with DT2W enabled) and a wonderfull touch experience.

Thanks Andy :good: ;)
[ONE Original Android Development] Maelstr0m:
no issue :)

tonight from 3am to 8am no drain after tweaking something with amplify :D
[ONE Original Android Development] otisman:
Much alohas and respect for the update and taking time away from the family for the oneplus one community
[ONE Original Android Development] AES256thetic:
To the people who are getting 7-8 hours SOT, what kernel settings do you use? I'm curious as I'm mainly getting 5-6 hours.
[ONE Original Android Development] unrated87:
Nice kernel Andi :D I'm using it for the last 3 days and ist awesome! Kinda funny that you also from Potsdam ;)

Grüße aus Potsdam West ;)
[ONE Original Android Development] andip71:
Hi,

yes, that is funny. I just moved to Potsdam this year in July.

I am in Potsdam Bornstedt, so maybe one day we can meet for a beer or a coffee.

Cheers

Andi
[ONE Original Android Development] Roman91:
hi Andi,

have you noticed that OnePlus has lower sensitivity of the screen compared to the i9300?

mmine loses a lot of touches

dont know if it's sw fixable

http://review.cyanogenmod.org/#/c/75570/
[ONE Original Android Development] andip71:
Yep, you are very correct.

I also had to get used to touch "stronger" onto this device.

So, absolutely, I have noticed that.

I am not aware of any fix for that. Might be even maximum sensivity of the hardware in the end. But I also hope this will be addressed in one or the other update.

I mean, they did a lot of improvements already in the touch screen area, so I am somehow optimistic.

Andi
[ONE Original Android Development] Leicxan:
Hi andi, on latest beta 5 my phone was hot , i didn't play game just browse the web.Do you have any idea about this?
[ONE Original Android Development] andip71:
No idea. But in 99% of cases this is an app running in the background, or media scanner going crazy or or or.

We would need to have betterbatterystats report or the output of a "top" command to see what is consuming the battery.

But I am sure, a reboot would fix your issue.

Andi
[ONE Original Android Development] Leicxan:
It seems Google service was eating my battery, usually i got power losing about 6.0%/h. I will reboot my phone to see if it will solve.
[ONE Original Android Development] OberstGrausam:
Guten morgen Andi,

great kernel. Tested it for the last couple of days and it's been really solid on latest temasek builds. I like your attitude towards kernel features so I'd like to know what you think about crossbreeder. Since it's the end of the month, a small donation is coming your way. Keep up the good work. Donation 7MU07601YD053303F

Grüße aus Hessen
[ONE Original Android Development] andip71:
Hi OberstGrausam,

hehe, what a nick name :D

First of all, thanks for the kind donation. Much appreciated, as always. You should have received your donation key already this morning.

Back to topic:

I am not a big fan of mods on top of a stable rom.

Crossbreeder was of quite big help on weaker (cpu power) devices as it was focussing on improving the entropy generation. This was achieved by the frandom module. If you are looking for just this, you do not need Crossbreeder but you can enable Frandom Entropy generator also in Boeffla-Config App.

But, tests have shown the OPO is so powerful, it does not give real benefits anymore - contrary to the S3 for instance.

Crossbreeder was then on top optimizing some other settings, mainly for low memory killer (LMK) and some virtual dalvik machine (vm) settings.

The OPO has more than enough ram, so I guess this part is also not neeed anymore and history.

And the vm stuff you can also tweak a bit by choosing the "Boeffla kernel tweaks" in the app.

It is as always - you need to test yourself if you feel a difference.

But I think whilst crossbreeder was still helpful on the S3, it is much more less on the OPO.

Cheers

Andi