yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] xTremePower:
Hy, I love your kernel !

but one question, how can I use your profiles ?

It's for faux kernel ? or other app ?

I can't find where to put them

Ps : I use Synapse with UKM (and don't find any profile files in synapse folder)

Thanks for you works !
[ONE Android Development] DespairFactor:
They are for synapse, they go into saved profiles folder
[ONE Android Development] stab244:
It doesn't work in faux clock. Only synapse. Which is odd.

Sent from my bacon
[ONE Android Development] DespairFactor:
We are switching to Sabermod tool chain on tonight's build! It will be rebased, which means some features will be missing

UPDATE: I am trying to add as many of the things I had in the previous builds into the first sabermod build. I will be dropping the abyssplug governors from builds now.
[ONE Android Development] TheShoxter:
Working great so far! Thanks for this.
[ONE Android Development] DespairFactor:
CM11S new build is up! Go get it!
[ONE Android Development] isosika:
Thank you for kickass kernel! Would you care to explain your different profiles just a bit, what they are for?
[ONE Android Development] DespairFactor:
I just try to make performance with battery in mind
[ONE Android Development] DespairFactor:
I am adding my F2FS liquidsmooth zips on this thread as well starting today! Just for all you F2FS fiends.
[ONE Android Development] DespairFactor:
You guys probably hate me for this, but there is another new AOSP build up now. 40_b02
[ONE Android Development] shiboby:
F2FS for cm11 too right?
[ONE Android Development] DespairFactor:
I made the F2FS liquidsmooth rom zip, F2FS support is in the kernel, but mods must be done at ROM level as well.
[ONE Android Development] Gi3M0:
Well, antutu gives a restart..

Sent from Oneplus one
[ONE Android Development] DespairFactor:
What kind of bug report is this?
[ONE Android Development] DespairFactor:
Rebased to stable branch and added the new touch firmware from CM, go get it! It is version 39 since we are running on stables now.
[ONE Android Development] shiboby:
So cm 39 is different From The cm 39 of a couple days ago?
[ONE Android Development] DespairFactor:
Yes, it has the new touchpanel firmware from CM in it
[ONE Android Development] :
[MENTION=5169465]RIPng[/MENTION] is there a v040_b04 version on it's way?
[ONE Android Development] DespairFactor:
Not right now, I need to cleanup my nightly branch before I can use it again, which is why I used stable for last release. I would say by end of day there will be a new release.

UPDATE: I lied, it will be up within the next hour if there are no build issues:)

UPDATE 2: I ran into bugs with new PPP stuff, will drop for this build.
[ONE Android Development] DespairFactor:
Sensei 40_b04 is now up! Go get it!
[ONE Android Development] oleg44:
will it be available for cm11s?
[ONE Android Development] DespairFactor:
Yes, I am working on it on my way to work
[ONE Android Development] shiboby:
Damn, you're hard core!
[ONE Android Development] ak:
Check here for fix it:

ak-11.0-nightly-experimental
[ONE Android Development] DespairFactor:
I will have to later on, I am building remotely on my phone

Sorry guys, CM11S update will have to wait until I am home tonight.
[ONE Android Development] oleg44:
thanks for all what you are doing, will be waiting!
[ONE Android Development] shiboby:
Hey guys. I'm having an issue with blx. In synapse I have it set to 98%, but it still fully charges. I though at first it might be displaying charged when it got to 98%. But after 5-7 minutes of use it displayed 99%. I'm running the cm11s kernel.
[ONE Android Development] kdrkdr:
Doesn't work for me either. Tested with different versions until version 39. Tested starting with phone off, while in deep sleep and with while screen on. RIPng promised to have a look "when having time".

p.s.: it worked the very first time I used it. Had Battery Monitor Widget running and could see the current drop when 80% was reached.
[ONE Android Development] Pipodi93:
I'm on 40_b04, on the latest SlimSaber and the phone freezes on the dialog "Android is upgrading..." and reboots... On stock kernel the phone boots, do you know guys why?
[ONE Android Development] Gi3M0:
Well I think this is a serious bug report.I`m using your kernel (latest version) with sabermoddes slim ROM (also the latest v..) everything on stock and just for curiosity I ran antutu and voila...reboot...for a couple a times?So...stability issues?..
[ONE Android Development] DespairFactor:
This I am unaware of, it's likely something with AK base

This is still not an adequate report. The bug could be with the app. Without any logs it's useless to report.
[ONE Android Development] Pipodi93:
Now I'm on latest version of AK, no problems so far...
[ONE Android Development] DespairFactor:
My kernel is ak with extra governors and blx atm. If you are using a Governor from ak there should be no issues from my code.
[ONE Android Development] Pipodi93:
Yep, I was using the Intelliactive governor... Could that be the cause?
[ONE Android Development] DespairFactor:
It shouldn't, but it's possible. I will look at adding any patches from faux for it.
[ONE Android Development] Pipodi93:
If it isn't, I don't see what could cause the reboots... I can't get a log, of course... I tried everything, from reflashing UKM, kernel and ROM, but nothing...

When I was on the 38, I didn't have this issue...
[ONE Android Development] DespairFactor:
Did you try another rom? Sometimes there are compatibility issues with rom and kernel. Also, was another governor tried? I need to know what testing was done to help isolate the issue. Feel free to dm me if you'd like.
[ONE Android Development] DespairFactor:
New AOSP and CM11S builds are up!
[ONE Android Development] Pipodi93:
I think that the latest update of the SlimSaber got some compatibility issues... I didn't test other ROMs, got back to AK's waiting for another build, hoping the issue will be fixed!

The previous configuration of my OPO was:

SlimSaber 20140907

Sensei v38

CPU governor: Intelliactive

EDIT: Just flashed the latest version of sensei, no freezes! Nice! :D
[ONE Android Development] oleg44:
thanks! but it seems last touchscreen firmware doesn't help, touch issues still here.
[ONE Android Development] artymarty:
I have a stock oneplus,

With latest software and patches (the public ones not nightly builds)

only change is TWRP recovery and it's been rooted. I can't seem to get this kernel to work, it tries to start up normal, just before the boot animation with the rotating part it vibrates and resets. Anything I'm doing wrong? I've tried both versions (asop and cm11s) same thing... Put my original kernel back, all ok.

I'd like to fix the touch screen issue as it's driving me insane.

Please tell me what stupid thing I'm doing...

Thanks
[ONE Android Development] DespairFactor:
Is it CM11S? Other people here are using CM11S fine with the kernel, maybe one of them can help you if that's the case, I haven't experienced this. If you could tell me ROM name and the steps you are taking when flashing, we can try to help you.
[ONE Android Development] shiboby:
Just and update that

Blx still not limiting charge

Only mistake I can see you're making is that you tried aosp. You need the cm stock kernel. I installed it just fine twrp, so make sure you follow op instructions.
[ONE Android Development] kdrkdr:
Do you use TWRP 2.7? There seems to be problems with 2.8
[ONE Android Development] TheShoxter:
Use TWRP 2.7.1.1. I had the same problem on 2.8.
[ONE Android Development] SupaKid:
On the latest Sensei 040b6, I have a weird bug.....: my audio disappears. Whatever I've set in Synapse prior to flashing the newest kernel are the same settings I set in the newest kernel....but my audio's gone.

*shrugs*

I don't know what's going on.
[ONE Android Development] f100cleveland:
Try disabling High Performance Mode in the audio section and rebooting.
[ONE Android Development] oriveradel:
Just toggle enable/disable SOUND CONTROL LOCK
[ONE Android Development] DespairFactor:
New AOSP build up!
[ONE Android Development] MontAlbert:
Installed the new build. Getting some weird graphics errors that I wasn't getting previously.

---------- Post added at 03:59 PM ---------- Previous post was at 03:58 PM ----------

Couldn't take screenshots as pressing the button got rid of the issue.

---------- Post added at 04:14 PM ---------- Previous post was at 03:59 PM ----------

This was coming straight from b04 to b06r2. Tried the first b06 and it did the same. Back to b04 and everything is ok again.
[ONE Android Development] ak:
You have to update your ROM.

ak@a0001
[ONE Android Development] DespairFactor:
Everyone I am going on vacation for the weekend, I will be back at some point on Monday. This means I will most likely not be building, unless I can actually get it to work easily from my phone.
[ONE Android Development] SupaKid:
That's a really nice Holden SS up there.
[ONE Android Development] Pipodi93:
Got this but too, but I don't understand this fix... I've got the Sound Control Lock on Enabled...Do I just need to set it on Disabled and reboot?
[ONE Android Development] oriveradel:
Leave it Disable
[ONE Android Development] Pipodi93:
And does it work? Do i need to set it on disable and reboot?
[ONE Android Development] SupaKid:
You can disable the option without reboot.
[ONE Android Development] Pipodi93:
I tried, but no fix. But when I rebooted the phone, the sound came back! ;)

Another question, do someone have a guide that explains all the governors in this kernel? I've found some guide, but the most of them are out-of-dated...
[ONE Android Development] NickosD:
Dat deep sleep...

Sent from my Bacon!!
[ONE Android Development] Pipodi93:
WOW! :D Nice! :) Can you share your settings? :D
[ONE Android Development] eliaspizarro:
same glitch, ive the latest rom from mahdi

back to 39
[ONE Android Development] Cris7ianO:
Thought id give this one a spin cause its based on [MENTION=3685904]ak[/MENTION] s awesome kernel. So far so good. I am liking the governor options and blx will be pretty cool I guess :) so thx for sharing:thumbup::D

I really feel like I am trained in ninjutsu, karate, taekwondo, muay thai and jeet kune do :p

Sent from my 1+1
[ONE Android Development] shiboby:
Since I saw a few pages back that you're working in v2.0, I would humbly like to request that you look into getting box to work on it. Thanks!
[ONE Android Development] DespairFactor:
Working in v2 of what?

I will be home tonight so expect a new build!
[ONE Android Development] shiboby:
Sorry that was a typo. I meant to say "working on v2.0" and by 2.0 I mean version 2.0 branch of this kernel :D
[ONE Android Development] DespairFactor:
New build is compiling, I will make a new CM11S build as well! Feature suggestion please for the next set of builds?:)
[ONE Android Development] DespairFactor:
Both new builds are up!
[ONE Android Development] shiboby:
It looks like blx is gone in the newest. Sorry, RIPng, if I annoyed you too much by asking about it a lot.
[ONE Android Development] DespairFactor:
It wasn't removed intentionally, I guess the merge removed it:s
[ONE Android Development] shiboby:
Then I humbly would like to request it be readded, if and when you want to and have the time to. I won't say anything more about it until then ;)
[ONE Android Development] DespairFactor:
It's one line to add it;) I can do it later today, just unpacking stuff from vacation!
[ONE Android Development] eliaspizarro:
same bug, ive the latest rom from mahdi
[ONE Android Development] DespairFactor:
This isn't a bug, your ROM needs to be updated to include the display fixes from CM
[ONE Android Development] DespairFactor:
Thanks for double post...
[ONE Android Development] eliaspizarro:
sry about that i was on my phone
[ONE Android Development] DespairFactor:
Fixed builds with BLX added and governor corrections are up now
[ONE Android Development] kdrkdr:
I can set a limit but the charge goes above the limit I had chosen. CM11S sensei.040_b08r2.opo.cm11s

[MENTION=4676584]shiboby[/MENTION]: does it work well in your config? If so, will you please tell the config?
[ONE Android Development] DespairFactor:
I still need to fix it, I haven't had time to actually fix BLX yet, if it is fixable that is.

UPDATE: I am trying a couple things, who is able to test on CM11S?
[ONE Android Development] DespairFactor:
Here is a new test build for cm11s to fix BLX, let me know if it works for you guys.

https://www.dropbox.com/s/ja597xleuzu9fpn/sensei.040_b08r2.opo.cm11stest.zip?dl=0
[ONE Android Development] shiboby:
Fully charged now, will give it a shot in the morning, thanks!
[ONE Android Development] Schrotty35:
Only for cm11s or have you a test build for cm11 too?
[ONE Android Development] DespairFactor:
I can cook up a CM11 one too, if you are able to test asap, I just need to know if it works:P I didn't want to make a test of both
[ONE Android Development] DespairFactor:
I am working on building an updater app for the play store. I will keep everyone updated on the progress, it is my first time making a java application, let's hope for the best.
[ONE Android Development] shiboby:
Good news: the phone limited charging to 96%. The phone stayed at 96% for at least an hour while on the charger before I disconnected.

Not so good news: it was set in synapse to 98%.

I have to go to work now but will do further testing later.
[ONE Android Development] NickosD:
Change cable and ac charger for start.

I have strange issue. After flashing kernel, can't take pictures. Gallery fc all the time...

Sent from my Bacon!!
[ONE Android Development] kdrkdr:
Thanks for your efforts. Unfortunately it doesn't work. Battery was on 50%. I put the limit on 55%. It's charging until 100%
[ONE Android Development] NickosD:
Change to ak and still the same. It could be rom issue. Will test later..

Sent from my Bacon!!
[ONE Android Development] ak:
The problem isn't related to kernel, reflash your rom and then Sensei.
[ONE Android Development] shiboby:
Try doing it again. This time, make sure you save the synapse settings, then restart the phone. Let me know if it doesn't work now.
[ONE Android Development] kdrkdr:
That's exactly how I did it. I also started with clearing all synapse settings.
[ONE Android Development] DespairFactor:
Is it working for you?
[ONE Android Development] shiboby:
It worked this morning, aside from being off by 2%. Trying it again with the same settings from this morning. I will report back in a couple hours.
[ONE Android Development] DespairFactor:
40_b12

New AOSP and CM11S builds are up!
[ONE Android Development] shiboby:
It didn't work all this time. Ill try the build tomorrow morning.
[ONE Android Development] artymarty:
Regarding: bootloops after installing the kernel

Thank you to all that helped (I clicked your thank buttons)

I can confirm, it was TWRP 2.8.0.0 causing the issue

I chaged to TWRP 2.7.1.1 then flashed the kernel, works like a dream.

Cheers! :good:
[ONE Android Development] :
Faux is teasing a new one. https://plus.google.com/109078966818501160423/posts/FcCDXGU8Jqo

Can you implement it?

Gesendet von meinem OnePlus One mit Tapatalk
[ONE Android Development] ak:
Is there source ?

ak@a0001
[ONE Android Development] DespairFactor:
Of course, I just need him to release it:)

UPDATE: Just send me a pull request or PM me or somehow inform me that it's up if you guys notice before me:)
[ONE Android Development] shiboby:
BLX Update:

So after working once with the kernel version you posted on dropbox (albiet limiting the charging at 96% rather than the 98% I had it set to in synaps), it didn't work the next two times I tried on that kernel. I then tried your newest kernel (b12), and it didn't limit the charging during the two times I used it. wierd...
[ONE Android Development] NeGriTa79:
Sorry, I have set the BLX 100%, but when I disconnect the phone from the office, after a few minutes, even if I leave the screen off, I shoot almost immediately to 99% ... it's a calibration problem?
[ONE Android Development] kdrkdr:
Weird indeed. I also have seen it working only once! Even installed another kernel (Franco) and Sensei again but no result.

---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------

Hmmm an accuracy of 1% is reasonable I think?
[ONE Android Development] NickosD:
Try to restart the phone at the next charge. Maybe it shows wrong number....

Sent from my Bacon!!
[ONE Android Development] mittimus:
Any chance for dynamic fsync in the next release?:D
[ONE Android Development] DespairFactor:
I am working on merging new CM code since AK in unavailable to do so at the moment! Please give me some time, I am also waiting on faux to release the code for intellimm, if anyone sees it let me know:)
[ONE Android Development] DespairFactor:
New build is uploading, brace yourself, we have display fixes, audio driver cleanups, GPU fixes/optimization and other optimizations.
[ONE Android Development] DespairFactor:
A quick update, I am also looking into making my own governor right now, I am unsure of how successful I will be since it is my first attempt. Wish me luck!
[ONE Android Development] Schrotty35:
Have install latest build and its so smooth all. Great work.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] _Beni_:
Having sometimes for some milliseconds graphics glitches

Sent from a OnePlus One with Mahdi's ROM and AK
[ONE Android Development] DespairFactor:
What Rom are you on?
[ONE Android Development] _Beni_:
Mahdi, on latest ak i didnt notify something

Sent from a OnePlus One with Mahdi's ROM and AK
[ONE Android Development] Lo4eath:
Doesnt work well with Droidkang 6.1 with UKM... i get these artifacts on screen on the b12
[ONE Android Development] DerRomtester:
Update your Rom or ask for an update. Cm made some good changes. Or disable hardware overlays.

Gesendet von meinem A0001
[ONE Android Development] DARKCHYLDX101:
+1 on latest Sensei Kernel, running nice on Carbon!

Exclusive Member of the OnePlus One Club
[ONE Android Development] TheShoxter:
I would recommend switching from DroidKang, I don't think it's receiving support anytime soon. You have the screen issues because the ROM hasn't received latest updates that address the problem. crDroid is what DroidKang is based off if you're interested in a good alternative.
[ONE Android Development] DespairFactor:
Your ROMs need updates because they don't have the display commits as DerRomtester stated.
[ONE Android Development] Lo4eath:
I'm actually thinking of going for the Heisenberg ROM. Gonna try it out with your latest kernel and let you know
[ONE Android Development] _Beni_:
It only appears on games not on normal things. Can someone explain me a watchdog bite and why it reboots after?

Sent from a OnePlus One with Mahdi's ROM and AK
[ONE Android Development] DespairFactor:
From what I have read it seems your phone is going idle and then reboots.
[ONE Android Development] Schrotty35:
I have crackling sound issus. But i dont know its kernel or rom related.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] DespairFactor:
Is high performance audio enabled?
[ONE Android Development] Schrotty35:
No. But whene i enabled there is also the same problem. I use PowerAmp.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] DespairFactor:
Same with other apps?
[ONE Android Development] Schrotty35:
I dont have test other player but will test now and report later.

Edit: with other player same problem.

Edit2: i have test now franco r20 and same sound issus. I think its a Rom problem.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] DespairFactor:
New build will be up shortly!
[ONE Android Development] DespairFactor:
Feel free to vote for my kernel to be default in AOSB;) I will support the builds! http://xdaforums.com/oneplus-one/development/aosb-t2842554

UPDATE: New build is up!
[ONE Android Development] Schrotty35:
I will test this rom with you new kernel. I hope this rom have not the sound issus. What will make high performance audio, i dont hear a difference to normal.

Edit: The last rom is from 2014-09-12, not so new and many new touch fixes are not included.
[ONE Android Development] DespairFactor:
Use the experimental build!
[ONE Android Development] kdrkdr:
Thanks! Cannot find the cm11s version. Any news about BLX?
[ONE Android Development] Schrotty35:
Have you a link, see only stable download link.
[ONE Android Development] DespairFactor:
CM11S was not update, only CM11, waiting on AK to update his.

http://d-h.st/QCZ
[ONE Android Development] MojoManagement:
Any other current difference than govs and blx?
[ONE Android Development] Schrotty35:
Thank you, download now and will test a little later whene i have more time.
[ONE Android Development] DespairFactor:
I have dropped blx for now, I will look into adding other stuff, but currently just govs difference between me and AK. AK already merges most of the stuff I like, which is why its so hard to find things to add on top.
[ONE Android Development] ak:
http://xdaforums.com/showpost.php?p=55599132&postcount=123

thansk man.
[ONE Android Development] Schrotty35:
I have 2 reboots. I have make log files.
[ONE Android Development] :
Every working fine for me, without the charging mode (charging without booted rom), permanent reboots, otherwise everything is fine! :)
[ONE Android Development] DespairFactor:
Guys check my github for new commits;)
[ONE Android Development] d13guit0:
you said the truth. You have put a lot of code today ;)

Good work mate!!!

Enviado desde mi One A0001 mediante Tapatalk
[ONE Android Development] DespairFactor:
Sorry guys, build will be up soon, just working on ironing out build errors:)
[ONE Android Development] B3L13V3:
Hey sensei, I was using your previous kernel built for cm11s, I noticed now you're AOSP...So is it safe to assume you won't be building kernels for cm11s?
[ONE Android Development] chikimonke:
He's thinking about it. See the previous page.
[ONE Android Development] DespairFactor:
After all that hard work I had kconfig issues, I have sorted them out and now it's building!
[ONE Android Development] SystemErrorOne:
Great Job OP you know who I am haha.. im on your G+ page :p

glad to see you working hard on your kernel. :good:
[ONE Android Development] d13guit0:
Good Job mate! You need a KitKat/pause

Enviado desde mi One A0001 mediante Tapatalk
[ONE Android Development] DespairFactor:
Sorry guys, I am fighting with hotplug errors now, I am hoping to have this issue resolved soon.

UPDATE: No luck yet, will need to rebase, all this fighting messed up the repo:/
[ONE Android Development] Fruktsallad:
Dude, get some well deserved sleep. We can wait. Just don't burn yourself out - that'd be disastrous for you and mean no more Sensei kernel for us. :P
[ONE Android Development] TheShoxter:
Yeah I don't think he knows how to sleep. He's been going on like 5 or less hours of sleep past few days :eek:
[ONE Android Development] DespairFactor:
There will be a new build today for sure, I am sorry I couldn't provide what I wanted to deliver to you yesterday, I am working on implementing the same features.
[ONE Android Development] Alin CG:
is it done yet? :D:D:D:D:D:D Can't Wait :D:D:D i need to flash something :D
[ONE Android Development] Setting.Out:
No need to apologize, what matters is that you take the time to build for us, we're on your schedule, you're not on ours.. :)

Sent from my OnePlus ONE
[ONE Android Development] DespairFactor:
I am testing each feature as I build to ensure it boots/works, I need better quality control this time.
[ONE Android Development] DespairFactor:
R2 is now up! Go get it!
[ONE Android Development] Vortex1969:
R2 running great here..Good Good
[ONE Android Development] DespairFactor:
R3 could be just around the corner;)

UPDATE: R3 is compiling now:) It will be up soon, the feature I added is a surprise.
[ONE Android Development] d13guit0:
Could be msm_hotplug?

Enviado desde mi One A0001 mediante Tapatalk
[ONE Android Development] DespairFactor:
R3 is now up! Can anyone guess what the new feature is?
[ONE Android Development] DespairFactor:
What?
[ONE Android Development] DespairFactor:
41_b07

New build is up!