yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] tracerit:
Will the new touchscreen driver work with CM¹1 also or only 11S?
[ONE Original Android Development] andip71:
I think only the experts writing the firmware can answer that. This is not readable for anyone.

Ha, was waiting for that for a long time (got it from time to time as well in the past years on the Galaxy S3 side).

Answer is: No. The flash function is not part of the app but part of the kernel. This is the only way to keep the app usable for all my devices without going into a maintenance disaster (for me).

The app has no concept of flashing nor which kernel it should flash etc, this is all handled within the kernel itself and saves me from lots of logic in the app.

Hope you understand. I cannot support "this lazyness" :D

Which is not a kernel issue !

Which governor do you use?

Well, I do not see a reason why it should not...

Andi
[ONE Original Android Development] cheungke:
Anyone know if my Rom build is 12/24, do I have to install the corresponding boeffla kernel? And where I can locate the previous versions? I looked on the site but the link was throwing a 403 error. Thanks much .
[ONE Original Android Development] andip71:
Well, I guess you are talking about a CM12 rom, correct?

Then 3.0-alpha9 is the kernel you need.

You can see all of that in the change log of the kernel on the homepage.

About the 403 error -this is fixed, forgot to put a user right on the "old" folder. My bad, thanks for notifying me.

Andi
[ONE Original Android Development] cheungke:
Yes, I was on this link earlier but was receiving a 403 when trying click into the "OLD" folder, it works now though. Thanks! [emoji3]
[ONE Original Android Development] schmitzekater:
Well I had the same issue yesterday. Tried to switch profiles and phone was unusable afterwards. I also had the circle "applying settings" two times.

Phone could only not be shut down just by pressing power 10s.

Will try to replicate.

App: 2.1.60, kernel alpha 10, temasek 4.0

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] TheQuarterMile:
I did a clean flash with alpha11 and used the 2.1.60 app and the problem got solved! And in case of lag before clean flash I rolled back the app to previous version and it worked fine.
[ONE Original Android Development] schmitzekater:
Just had it again.

Was switching presets when phone became laggy and didn't response at all finally. Forced reboot and after boot it rebooted once again.

Stable since then, but I captured a log.

Temasek 4.3,alpha 11 and Super Su 2.43
[ONE Original Android Development] andip71:
2 quick hints after seeing the log and your configuration:

- do not use undervolting (usually I refuse to give any support when I see undervolting in place as this makes everything unpredictable)

- try to switch back to default hotplug profile for some more tests, instead of optimized

Andi
[ONE Original Android Development] schmitzekater:
Yeah, thanks for your reply.

Usually I don't undervolt, it must have come there by loading presets in your app. ;)

Sonn after restarting it rebootet once again while using G+.

After restart I saw that the memory was pretty much loaded (only 116 MB left). Could that be the issue and a problem?

Anyway, I'll attach that log and won't post again if UV or OC are involved.:cowboy:

Thanks and have a nice day.
[ONE Original Android Development] andip71:
Honestly, if you have that heavy reboot issues, something must be completely wrong.

Do not know if it is the combination of Temaseks CM12 with my latest kernel, as I only use Daleski75 builds (I know there is nothing added in there, so it is my reference).

And with that, all is fine (for me).

Anyways I will bring alpha12 still today, maybe this brings you back on track finally.

So far, we have to accept CM12 is still not even official nightly, so all can happen :)

Andi
[ONE Original Android Development] schmitzekater:
No worries, I don't blame the kernel, as it was the first kernel for me that serves well without rebooting while playing Ingress.

And I don't blame CM12, as it is still alpha as well.

I'll keep tinkering and see what suits best. So far I guess I had no reboot with the zzmove governor, seems to be my sweet spot.

Just downloaded the updated app and I have a small suggestion, don't know if it was stated earlier: When swiping thorugh the app it happens to me that I change sliders, i.e. setting min freq to 1497MHz. WOuld be nice if the app would ask me to save the changes to the current profile.

Again thanks for your work and patience. :angel:
[ONE Original Android Development] fjsferreira:
Just a quick heads up, using latest teamsek and latest boeffla here, not a single reboot whatsoever. Using stock boeffla settings, except raised the headphones volume a bit.
[ONE Original Android Development] andip71:
Thanks for the suggestion. But my philosophy with the app is to be "quick" without pressing apply all the time.

Also it would mean a complete UI revamp of the app, which I do not have time to do, and not the big motivation :)

If you have trouble with swiping, you can disable swiping in the settings. So you have to change tabs by clicking on them in the header.

This is at least my more preferred option....

Cheers

Andi
[ONE Original Android Development] schmitzekater:
Ah, didn't know about that setting. :good:

Thx and changed. :D
[ONE Original Android Development] andip71:
New kernels for all variants

Good evening,

all three kernels (CM12, CM11, CM11s) receive a small update now.

Nothing major, just preparation for GPU control (incl. GPU overclock, but also underclock) and the new touchscreen drivers everywhere + updating to last CM code base.

Note: The GPU stuff is in, but not yet activated. I still want to give it some testing and will enable it with a new Boeffla-Config app when it is time for it.

Here we go:

CM12 - Version 3.0-alpha12

05.01.2015

GPU control incl. GPU overclocking prepared and in, but not yet activated (I will test a bit more first)

Ramdisk updated to inofficial CM12 build of 05.01.15 by daleski75

CM11 - Version

2.0-beta16

05.01.2015

Touchscreen firmware update 14001222 from CM12 branch incorporated

GPU control incl. GPU overclocking prepared and in, but not yet activated (I will test a bit more first)

Updated with latest 4 CM kernel commits for CM11 by 02.01.15 (0d1e3227)

Ramdisk updated to version of nightly 05.01.2015

CM11s - Version

2.0-beta16

05.01.2015

Touchscreen firmware update 14001222 from CM12 branch incorporated

GPU control incl. GPU overclocking prepared and in, but not yet activated (I will test a bit more first)

Have fun!

Andi
[ONE Original Android Development] Mrj0to:
Set 2 cores on in boeffla app. That will probably fix it.
[ONE Original Android Development] singhz905:
I'm having the same problem with Tunein Radio and Setting 2 cores didn't fix it.. :'(
[ONE Original Android Development] andip71:
Which governor do you use?

Is it only when screen goes off?

What about when you increase the CPU min frequency to 422 or higher for a test?

Andi
[ONE Original Android Development] singhz905:
I'm currently set on Interactive [standard]. and yes it stutters only when screen goes off.

I just tried it with CPU min frequency as 422 + Hotplug profile as Default and it's working flawlessly.

Thanks once again Andi

Edit:- I was actually on Interactive [battery] when I was having problem. Now I tried it with Min frequency set as 268 with Interactive [standard] and Everything is playing fine. No probs now. I guess that battery saving governor profile was creating problems.
[ONE Original Android Development] dickenam:
Sorry if this has been explained before, I searched before I posted - promise!

Hotplug tweak profiles (Default, Optimized, 1 core, 2 cores, 3 cores, 2 cores on, 3 cores on, 4 cores on) -- What's the effective differences? I'm kind of confused (Is Monday, I'm slow) :good:
[ONE Original Android Development] spanish33:
[MENTION=947981]Lord Boeffla[/MENTION] with your kernel installed on slimlp I loose the ability to dt2w, however with slimlp kernel it works.

The rom doesn't have an option to enable dt2w so I am not sure if it is enable in the kernel.

Swipe to wake and sleep however works but not dt2w.
[ONE Original Android Development] orangerot.:
Its working fine on temaseks cm12. So I'd say it's a rom issue.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Yes, I can imagine slim put again something in which breaks compatibility with cm12. Would not be the first time...

Sorry, but as long as it works fine on "normal" CM12 roms, there is nothing I can do (and nothing I want to do).

Supporting every rom flavor is just impossible.

And of course the kernel supports dt2w,other it would not work on cm12 too.

Maybe slim has an extra special implementation of it.

Previous Boeffla-Kernel have the same issue with your slim version?

And one more: have you switched the function on to prevent accidental wake up somewhere? If yes, try without.

Broken proximity sensor is currently a big topic, funnily it can only be resolved by flashing a lollipop alpha modem. Maybe it is the same here...

See Daleski75's cm12 thread for more information on that.

Andi
[ONE Original Android Development] spanish33:
Ok I understand. No dt2w never worked with your kernel on slimlp so it is definitely a rom issue I will wait for it to be fixed.

Yes I have the alpha modem and accidental wake is turned off.
[ONE Original Android Development] matius44:
D2tw is woeking perfectly fine for me on latest SlimLP with boeffla kernel, and it has always been working since I converted to SlimLP mid December.
[ONE Original Android Development] abhibnl:
Andi, is it possible for you to build new version without updates touchscreen firmware? I don't know but it seems new drivers aren't as responsive as the current ones. I can feel it overall the UI and even on DT2W. It even miss touches sometimes. I guess as if now, i'm the only one with the issues. There's no major bug overall but it seems the latest drivers are not as responsive as the older ones.
[ONE Original Android Development] silvagroup:
Completely understandable.... Thanks.
[ONE Original Android Development] magnamentis:
i hate to say it but unfortunately i and obviously many others come to the same conclusion. it took them half a year to come up with reasonably performing touch drivers which even in their best iteration never reached the standard of many years on any device in full and now they really made it to come up with an at least one if not two steps back version. sometimes i doubt if these guys ever use what they produce, i mean the moment i installed that new touch drivers i could feel the difference, missed touches, dt2w only on second or third attempt while it was working really, almost pefectly well before that. just don't get it how often people change winning teams and/or working technology to the worse.
[ONE Original Android Development] DooshPastesh:
So, it must be hardware related becouse mine opo screen is running great from the very beginning..
[ONE Original Android Development] abhibnl:
Hmm! well that seems legit then. I already rolled back to beta 15, Hope andi will make a version without updated drivers. New drivers are not well polished at all.
[ONE Original Android Development] P1nGu1n_:
Yeah probably. Only in the beginning when typing too fast it saw this as a swipe, but this was solved with the next update. Apart form this I never had any other problems with my touchscreen, always been responsive to me.
[ONE Original Android Development] magnamentis:
yeah the suspicion that some hardware had flaws was there from day one and yes it's intermittent, depends on uptime to a certain degree and is not as bad for some than for others, i've seen horrible screenshots with proof in the beginning, but however it got really 99% solved, just had to be a bit more precisely hitting the spot than with my other 6 devices, otherwise i perhaps at the end would not even have recognized the difference anymore. i'm using 3 devices daily for different purposes and the difference is and was there, just that now it got worse, and again not for everyone obviously.

however thanks for sharing you experience, my point was less the impact itself because in my case it's not thaaaaat... bad, but the fact that it god better and better over 6-7 months and now suddenly went backwards :) some of it i can correct by raising the min. cpu frequency to 422 and by using more aggressive governors. with ak i was changing gpu gov to performance while i'm not sure what the lord has set for gpu gov. anyway, it's ok just a pitty that it was even better before "only for some as we already agreed upon"
[ONE Original Android Development] molonad:
I know my question doesn't include this thread but I need quick answer, iam sorry What will happen to my files when I will flash new rom, Wil they move somewhere? Becouse it's ridiculous that they will just dissappear? What I will have to do with apps data?
[ONE Original Android Development] HaTrED_:
Mate, you're posting that same question through various threads! I would advise you some reading before start doing anything...
[ONE Original Android Development] molonad:
I know sorry, I will not do it if I will have more time.. I didn't do this, and I will not do it anymore
[ONE Original Android Development] spanish33:
Hmm even after a clean install it doesn't work for me.
[ONE Original Android Development] Fenvarien:
It's working great with the new touch firmware here too. Maybe it really depends on the specific hardware revision.
[ONE Original Android Development] miguepereira77:
Definitely must be hardware, as I did not have any weird touch issues or yellow screen since I got mine in November ( so it's pretty new) using different Roms, kernels, modems and what not...
[ONE Original Android Development] singhz905:
Hey Andi, i'm facing that problem with audio stutter again when screen is off. I've tried all the combinations. My current cpu min freq is set as 422 and its still stuttering. Any possible fixes?
[ONE Original Android Development] andip71:
Well, that's fair enough.

As nobody can read what is inside a new firmware, we have to trust they improve it and do not make it worse.

I personally have zero issues with the new touchscreen firmware on all my phones here, but of course this is not representative. And yes, I got some more complaints about the touchscreen since last kernel version, so I have no problem reverting that back again as it also does not do any specific good to my phones. It just worked as before, not better, no worse. So I do not lose anything by reverting it.

HOWEVER: Before I do that publicly I would like the affected guys here to test a test kernel with the reverted firmware first. Just to make sure it was really the touchscreen firmware causing it and nothing else.

So, I will provide you with a link to a test build for cm11s and cm11 in a PM now.

Not any fixes I could provide you anymore.

I mean, cm11 and cm11s: I never had any audio stutters at all.

But this topic is as old as there are Android smartphones around, it is/was the same on Galaxy S3, Tab 10.1 and so on.

For some, increasing min CPU frequency helped, for some it helped to play around with readahead buffers (in fact reducing it!!), changing governors and so on... It is a big play ground.

Appartently it also has a LOT to do with processes running in the background, sync tasks, apps that do something etc. Otherwise everyone should have exactly the same problems - which is not. Also it seems to depend alot on the used player software. So I am afraid, I cannot give you any more conclusive hints at the moment.

For CM12 - yes, expect anything here. Everything is alpha, not even nightlies, both on rom and kernel side. Especially the audio section is known to be a big area with lots of work still ahead.

Andi
[ONE Original Android Development] andip71:
This question should be asked in rom threads, not in kernel threads please.

Andi
[ONE Original Android Development] Almayce:
Well I just set "2 cores online" in boeffla app and every stutter is gone.
[ONE Original Android Development] andip71:
Thanks.

Shows just again, that every OPO, setup, installation, user, behaviour... reacts different.

For you this is the solution, others need something else. Hence, there seems to be no general advise for it.

So, it confirms what I wrote before :)

Andi
[ONE Original Android Development] kurtextrem:
Don't forget to test with a placebo build. Don't tell them which contains the new and which the old. Only that way we'll know if there is a difference ^^
[ONE Original Android Development] andip71:
LOL, honestly, I did that some times in the past for the Galaxy S3 kernels. With quite interesting results. But in the end, you had too many different opinions to make a conclusive judgement.

This time it is simple. Better or not.

And I got already reply from a German user that complained about the same, reverting to previous touch drivers sorted his ghost touch issues again.

So I am waiting for at least one more result from a XDA user on it, then I push a new kernel version out.

By the way: CM12 kernel will also most probably come in a last alpha today.

According to this CM announcement, I can transform it into beta1 very soon :)

http://www.cyanogenmod.org/blog/the-l-is-for-lollipop

Cheers

Andi
[ONE Original Android Development] merikgvr4:
LB your alpha 11 is awesome. Using intelimm gov. Snappy performance. The best battery life I've gotten so far. Using FJ's SS LP ROM. Don't want to update to a newer kernel anymore. Hope the next charging cycles get even better.
[ONE Original Android Development] beany>:
Good times. And theme engine should be here within weeks is great news.

I also find it amusing that after the fallout between OnePlus and CM that bacon is the first device listed. Part of the "kiss and make up"? lol
[ONE Original Android Development] P1nGu1n_:
First nightly is already available: https://download.cyanogenmod.org/?device=bacon&type=nightly :)
[ONE Original Android Development] andip71:
Yes, I saw it.

And first beta1 kernel is already on my harddisk.

I am just waiting for one little more feedback on the touchscreen driver revert, then I am ready to pump 4 kernels out straight away:

cm11s and cm11 beta17 (reverted touchscreen drivers)

cm12 alpha13 for inofficial cm12

cm12 beta1 for official cm12 nightly

I hope one of the two test users can quickly give some feedback, but I am not even sure in which time zones they live. So, all is ready and waiting to go.

Andi
[ONE Original Android Development] r0hit.s3n:
[MENTION=254166]Lord[/MENTION]

may I ask if ur cm12 beta1 will only work with cm based rom like tamasek, or will it also work with aosp based like euphoria
[ONE Original Android Development] andip71:
It should, however I am only testing against CM.

Andi
[ONE Original Android Development] matius44:
That's weird. The only thing I can think of is that I was running Tyr kernel before flashing Boeffla, and with Tyr kennel I sat dt2w with synapse application.

Then again, I re-flashed SlimLP before flashing Boeffla kernel so theoretically there shouldn't be any settings left from Tyr kernel.
[ONE Original Android Development] r0hit.s3n:
being an vivid fan of ur kernel ever since I started using it few weeks back, never hoped onto any other kernel

just wonder ur alpha build where so spicy what will the main course beta version will serve as

and thanks for this wonderful work of art

Sent By MyOne+

Devil Inside®
[ONE Original Android Development] andip71:
Naaa, let's hope so.

It is ready there to go, see screenshot.

As described above, I will wait for some more time if there comes some additional feedback from the guys with touchscreen issues. But if not in the next 3 hours, it will go out anyways.

Andi
[ONE Original Android Development] LeroViten:
Hey, Andi, I was always wondering why so many kernel sources aren't updated to 3.4.105? ??
[ONE Original Android Development] singhz905:
Hey Andi, I did some tests and guess what I found out. I'm the one to blame for all that stuttering sound. I un ticked the keep awake and wakeup options for my music player and tunein radio in privacy settings.

Now i have set them to default. Everything is working perfectly fine on stock settings.

Sorry for bothering you.
[ONE Original Android Development] andip71:
Because the benefits of upstreaming Linux to a higher minor version is highly overrated. I did that for my S3 and Tab 10.1 kernels most of the time.

Effect was almost zero, more new bugs introduced than others fixed.

It is important for Linux, less important for Android has a majority of the new code is not used there.

My opinion based on experience.

When I am feeling really bored one day (which will most probably never happen), I will also upstream. But I do not see any valid point for it, especially not balancing out the risk of breaking working stuff by it.

Ok, then we blame YOU now :)

Lol, just kidding. Hope this time your solution is sticky and you are happy.

Andi
[ONE Original Android Development] abhibnl:
Check your PM bro!

Sent from OnePlus One Powered by Boeffla
[ONE Original Android Development] andip71:
Kernel update

Hi all,

due to the fact, the new touchscreen drivers from the CM12 branch do not seem to work perfectly fine for everyone, I decided to revert them back in the kernels again.

And also due to the fact, CM finally released the first CM12 nightly, I will provide a CM12 beta kernel from now onwards.

So this is what we have now:

CM11/CM11s - Version

2.0-beta17

06.01.2015

Reverted CM12 touchscreen update 14001222 (it was obviously a step back for a few users with specific hardware)

Disabled diagnostics driver as it is not needed (also disabled in CM12 already)

CM12 Unofficial roms up to yesterday - Version 3.0-alpha13

06.01.2015

Updated with latest 9 CM kernel commits for CM12 until 06.01.15 (0a88dcf)

Reverted CM12 touchscreen update 14001222 (it was obviously a step back for a few users with specific hardware)

Partial panel updates enabled again

Ramdisk updated to inofficial CM12 build of 05.01.15 by daleski75

CM12 official CM nightlies - Version 3.0-beta1

06.01.2015

Note: This is the version you should use with the first CM12 nightly !!!

Replaced by ramfs of first official CM12 nightly of 06.01.2015

As always, enjoy!!

Andi
[ONE Original Android Development] kalpik:
Thanks! Much more responsive touchscreen with the revert! Though don't totally understand the difference between alpha 13 and beta 1. Aren't they both for cm12 based ROMs? Is the difference only the ramdisk?

Sent from my A0001
[ONE Original Android Development] andip71:
Yes, exactly. I just used the official nightly ramdisk for beta1.

In theory, beta1 should run also on the older inofficial builds. But in case not, alpha13 is the version to use then.

I made alpha13 more to give it a proper closure.

Cheers

Andi
[ONE Original Android Development] Spewmonic:
Typical me. Download and flash first before even bothering to read the post.

Great. *whacks self*
[ONE Original Android Development] magnamentis:
just thanks

ok, looks like if i am a bit late, late sleep, late wake, late testing :) just wanted to let you know that it's better with the reverted drivers.

absolutely no doubt about that. smooth and reliable dt2w again and all the rest is well also. thanks for taking care. it looks a bit that it was the first few batches of device production facing this. most users who are reporting little or no issues purchased in late summer or even later.

cheers

EDIT: applies to both cm11 and cm12 based roms with this kernel
[ONE Original Android Development] Texan1:
Hi mate, sorry but I'm a bit unclear as to which I would use with slimsaber rom (LP 5.02)?

http://xdaforums.com/oneplus-one/development/rom-slimsaber-bacon-t2858033

I assume version 3 alpha 13?
[ONE Original Android Development] andip71:
I dont know for sure, but I would give that a try.

And next time maybe beta1 already, after slim pulled latest updates in.

Andi
[ONE Original Android Development] Fenvarien:
Just a quick info for users of custom CM12 ROMs: The latest Boeffla kernel beta 1 works here perfectly well even with Temasek's ROM 4.2 (build date 03.01.2015).