yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] 11wallace11:
Latest CM12s beta10 version combined with zzmoove (optimal profile) and sio scheduler gives me the best performance/battery life i ever had on this device.

This is amazing! Thank you very much!

*Just to be clear, battery life on cm11s used to be better, but cm12s has this Android System battery drain problem which is not a kernel-related problem.
[ONE Original Android Development] TorchaOne:
Okke. I had weird errors:

06-03 09:03:52.891 E/MP-Decision( 3888): Error(-22) changing core 2 status to offline

06-03 09:03:52.891 E/MP-Decision( 3888): Error(-22) changing core 3 status to offline

06-03 09:03:52.924 I/MP-Decision( 3888): Error locking minimum cores

zzmoove - optimal. I changed to interactive, no error anymore and then back to zzmoove and its cool now.
[ONE Original Android Development] andip71:
Informational only, no need to worry.

As said, we are not allowing mpdecision everything when certain hotplug profiles are selected.

Also, nobody knows what mpdecision logs in logcat, it is closed source.

So, ignore it and stay happy.

Andi
[ONE Original Android Development] TorchaOne:
Ok. I was just testing catlog sw and noticed those. Lots to learn still... huhu. Thanks.
[ONE Original Android Development] tr0ner:
There has been another commit from CM Team in yesterday's nightly:

synaptics: Fix find7 compilation (android_kernel_oneplus_msm8974)

Is this another update to the touchscreen driver?
[ONE Original Android Development] andip71:
No, not for our OnePlus One device.

It is for the Oppo Find7, which uses the same kernel repo as our OPO.

This fixes a compile issue on the Find7 which we never have/had for the OPO.

No new firmware contained for any device in that patch.

Andi
[ONE Original Android Development] tr0ner:
Danke Andi =)
[ONE Original Android Development] kurtextrem:
I was on that before and gotta say Zen gives more fluidity :)
[ONE Original Android Development] andip71:
And I prefer tripndroid in the past days somehow. Just belly feeling though...

Andi
[ONE Original Android Development] Clark789:
For a long time in the past i used zen as well. And then i went to row and liked it pretty much, because i think, it's a little bit more fluid than zen. For a few days i try tripndroid and so far i don't see a big difference to row... Just my 2 pence or bananas or whatever...

Cheers

Clark
[ONE Original Android Development] fmc000:
Me too.
[ONE Original Android Development] andip71:
The only "concern" about ROW I have is: Row means "read-over-write".

So when you for instance have heavy write access to the sd memory (e.g. recording a video), read requestes could lead to interruptions/stutter etc.

Have not seen that on the OPO so far, but it was a topic on the slower S3.

Andi
[ONE Original Android Development] hp13:
bother to let it be? it's XDA. freedom of speech/though is allowed.
[ONE Original Android Development] Freddy1X:
And you got good battery life with it?
[ONE Original Android Development] anshumandash:
What's the difference between default hot plug and optimized hot plug?
[ONE Original Android Development] truewt:
5.1
[ONE Original Android Development] andip71:
Default let mpdecision hotplug how it wants, this means in idle many times two cores are on although not needed.

Optimized makes sure, in idle only one core is plugged in by mpdecision.

Andi
[ONE Original Android Development] lchiocca:
To all the people that were having dhcp issues.... the proper patch has been sent to review. From the looks of it, CM are planning to get this fixed in 12.0 and 12.1 :)

https://jira.cyanogenmod.org/browse/BACON-3269

http://review.cyanogenmod.org/#/c/100138/
[ONE Original Android Development] Clark789:
Yes, true. But in fact most of the time my OPO is reading. Heavy write access only happens, if i copy a movie for my son to my phone... ;) And i'm quite seldom so nice...

So, i made really good experiences with row.

Cheers

Clark
[ONE Original Android Development] mrhamed:
I don't like mandatory donation :\ So back to AK kernel
[ONE Original Android Development] Shadow Samurai:
Was on Franco r42 for the longest time. Made the switch to this yesterday because of the screen fix, even though it was barely noticeable on my OPO. Anyway battery life seems to be fine and the phone feels much more stable from touches.

Great job.

Running cm12s with latest beta.

Sent from the one and only Oneplus One
[ONE Original Android Development] gondsman:
How is the donation mandatory? It only unlocks fairly minor features in the app (and you could tweak them with an init script anyway).
[ONE Original Android Development] andip71:
Donation is not mandatory, I do not know what rubbish you are talking.

Everything is free which you need for daily job.

Everything else is not true.

I don't like users that spread wrong information because they have zero clue.

Andi
[ONE Original Android Development] davebugyi:
Go back and have fun, but please LEARN to read :o
[ONE Original Android Development] fmc000:
First ever soft reboot Yesterday on CM12.1 - probably a coincidence but I had enabled prevent accidental wakeup just a few hours earlier.
[ONE Original Android Development] magnamentis:
no, reading and searching are required = a must !

no freedom to ask for being spoonfed !!! that kind of freedom is an illusion !
[ONE Original Android Development] andip71:
Most likely when you did not have any before.

Monitor it, next time create a debug info file, then we can have a look.

Andi
[ONE Original Android Development] suaverc118:
Is it possible for a kernel to keep mobile data on while screen is off, data and WiFi toggled off? My phone was not awake at all, but mobile data stayed on. Lost 10% over night with latest bliss and Zane's u600 version of your latest kernel. Before Google app and mobile radio killed me, now its something different. According to gsam there was nothing major. I did block some wakelicks through the bliss dev options too.Thanks for any feedback.
[ONE Original Android Development] magnamentis:
honestly speaking, albeit such issues are hard to tell for sure and immediately what causes them, i had the same issue with the last two version of blisspop and reverted back to the 27th of May version, still 3.4, and issue is gone. to make it clear, i use the same kernel v4.0 Beta 18, i just flashed the 27th blisspop version over the 2nd of June version and after 3 consecutive days with 20-32% battery loss in idle over night was gone and the culprit was definitely phone idle "IN AIRPLANE MODE" very strange. so i cannot say what the issue is, can be rom side in combo with a kernel or only rom side which i suspect but such statements are prone to backfire haha.... so i tend to solve things the way i did, flash back the last working version and wait vor new versions and check if the issue persists or has gone. no point in causing a gathering of a million opinions and it's defefenders LOL
[ONE Original Android Development] andip71:
All I can say is: The kernel does not control mobile data, whether it is on or off.

This is handled by the radio (modem) together with the rom, the kernel is just the communication channel.

I suspect clearly an issue in the rom handling here.

Especially as I do not have on official CM12.1.

Andi
[ONE Original Android Development] suaverc118:
Thanks fellas. No way blaming the kernel, just trying to narrow it down. Man I was so happy to have fixed an issue, then this one happened. I love the kernel BTW. I'm so used to having on average 8 hours of SOT, now I get about 5 hours. Maybe I should go back to an older ROM, but I also notice not others have the same issue. [MENTION=5372360]magnamentis[/MENTION] seems to have a good deal on his ROMs, I envy you sir. Lol
[ONE Original Android Development] gondsman:
Also, if I can add, the wifi drivers are really misbehaving since we moved to lollipop. This is of course not a specific issue of this kernel, it's the same drivers the official CM kernel uses.

When the screen is off my phone randomly disconnects from wifi (as in, the wifi actually turns off for a short time, you can clearly see it in the battery graph). It seems to happen mostly when I'm at work where the local network is kind of an edge case (we literally have tens of thousands of devices connected to the same LAN), but it also happens less often while at home.

The main issue is that when the phone loses connection it issues a wakelock to reconnect and at work this happens so often that it eats my battery. I have 25% awake time when not doing anything with my phone just because play services (and to a smaller degree facebook) keep trying to reconnect to the network. At home if I leave my phone with the wifi on during the night it idles at 5% awake time, in comparison.
[ONE Original Android Development] andip71:
I am tempted to compile the latest CM11 drivers into a CM12.1 test kernel.

Not sure if it makes any difference, however would be interesting to test out.

Would you volunteer to give it a try? Hehe.

Andi
[ONE Original Android Development] gondsman:
Yes, of course. I didn't remember seeing anything like this when I was on CM11S. I actually skipped CM12 and went directly to CM12.1, but I could see other reports about this, it seems like a very well known issue. I think it is worse in my case because the LAN is very "noisy" so it probably takes a while to get a connection and/or it's less stable.

I have to say that it's still better than my old note2 (you know the device very well I think), which had this freaking non-working packet filter which caused the phone to be 50% awake while at work just from receiving random broadcasts on the network.
[ONE Original Android Development] andip71:
Yes, this information is spread everywhere.

But was no dice, did a test compile and drivers turned out too old to work with CM12.x environment unfortunately.

So, we have to wait for proper fixing :)

Andi
[ONE Original Android Development] 11wallace11:
I tried Zen today. Unfortunately, I got worse performance AND battery life.

Back to sio ;)
[ONE Original Android Development] andip71:
Give tripndroid a try... just a suggestion.

Andi
[ONE Original Android Development] Nami_Girl:
OPO - CM12s : the kernel is good and there are a lot of options for CPU ext but there aren't the options about display (saturation , contrast , ect) . Why ?
[ONE Original Android Development] RcrdBrt:
I just want to put in here some infos about I/O disk scheduling.

Few weeks ago I spent a day with BFQ-iosched developers. It was a fantastic experience which I wrote down here.

And 2 weeks ago I participated at a workshop organized by Micron technologies, an industry world-wide leader in the production of memories. There I had the opportunity to talk a bit to a Linaro guy (the actual maintainer of the eMMC drivers at Linaro) about storage devices and power-saving solutions. So a period of my life in which I/O disk schedulers were the main topic :D

I'm not going through technical problems and features. But I have to say this: despite of being a bit underestimated, I personally think that BFQ so far is the most advanced I/O scheduler out there and it will be the actual standard in a near future. So there's no point about the "Fancyndroid" thing or whatever (with all the respect given to the developer, of course). There are such huge studies and heuristics behind managing the I/O that a "straight" scheduler that essentially does nothing (such as noop or SIO) can't simply work for the best user experience. It may work better just in the benchmark land.

I'm not saying "omg BFQ iz the besttt try it!", I'm just saying that it's the only one that tries to go beyond the standard queues of processes, guessing what's the best process in that moment that needs I/O priority. An extensive usage of it can only be beneficial in terms of bug fixing and heuristics improving.

1) It will soon be included in the linux kernel mainline. There's still a debate whether it will be called BFQ or it will patch CFQ → this is because BFQ was originally built forking CFQ. But at the moment (v7r7) the codebase shared between the two is so low that it would be a nonsense calling it CFQ (although the CFQ maintainer wants this thing, of course).

2) there are talks of implenting it INTO the memory controllers, in order to use its algorithms with every peripherals that access the memory.

For this 2 reasons it may be worth a try. I did it and I'm enjoying it on my PC and on my OPO. There are a lot of situations in which BFQ behaves actually better than the others.

P.S: v7r8 will be published very soon (it already completed the stress tests successfully) with a big fix and minor issues resolved.
[ONE Original Android Development] andip71:
Because I have only implemented the RGB colour control.

And as many times said, I have no intention to implement anything else in my kernel.

Thanks

Andi
[ONE Original Android Development] anshumandash:
I am using it and the phone feels fast and responsive [emoji106]
[ONE Original Android Development] mp3deviant721:
Use a ROM with LiveDisplay if you want that. Otherwise its gotta be a different kernel.

OnePlus One | EuphoriaOS x Boeffla edition™
[ONE Original Android Development] andip71:
Thanks for your comprehensive and detailed message.

I also think, BFQ is widely underestimated and great work has been done here with a lot of fine tuning etc.

However, one important fact for me (personally) is not only theory on paper but also the "feel-good factor". And this is where I like tripndroid most at the moment. It just feels good, not heavy, gives me smooth experience.

Although I agree BFQ is probably much more sophisticated, tripndroid just does the job perfectly for me at the moment. And this is an important fact too.

But hey - thats why we have the choice here and I included BFQ for more than 2 years in all my kernels anyways :)

Andi
[ONE Original Android Development] Nami_Girl:
What a pity , it would be a very useful option .

Inviato da Mountain View
[ONE Original Android Development] andip71:
For some yes, for some no. For me absolutely no, I do not even use the RGB controls, I am not color addicted :)

For me no, and there are more internal reasons why I will not implement it.

But there are enough kernels around that have it. Just jump over there.

Thanks

Andi
[ONE Original Android Development] alexbk66:
Do you expect the dev to work for free? Boeffla kernel is the best, I tried many of them. But yeah, it's your choice.
[ONE Original Android Development] andip71:
But still,

everyting

is free.

All functions that are unlocked in the donation app version can be achieved simply by using other apps as well. They only add some nice-to-have comfort functions.

This is very important to me to keep all required basic functions always free.

Of course, there are generous people that appreciate the time and efforts going into all that projects, and they can donate if they want.

I think it is just fair to show them also my appreciation back and give them a little bit more comfort.

That's all about it :)

Andi
[ONE Original Android Development] alexbk66:
Completely off topic, but couldn't resist, regarding BlissPop: HAHAHAHA I can't stop laughing at how these fools fell for it!
[ONE Original Android Development] kurtextrem:
I wonder if it's only me or takes it slightly longer to turn the screen on when using tripndroid compared to zen / sio?
[ONE Original Android Development] suaverc118:
Hey turd, can't view it, you blocked me because you couldn't take what I said before. Anyways, grow up.
[ONE Original Android Development] mp3deviant721:
I don't think I/O would affect the screen on time. That'd be more of a governor issue.

OnePlus One | EuphoriaOS x Boeffla edition™
[ONE Original Android Development] BigFuzzyBush:
[MENTION=1045701]lordboeffla[/MENTION] What governor do you like to use when using tripndroid? Any other particular setting you care to share so I can mimic yours and see how she does? Kudos for the amazing Kernel BTW. Been running your kernel since day 1 of owning my OnePlus.
[ONE Original Android Development] gondsman:
I gave this ROM a try: http://xdaforums.com/oneplus-one/or...l-unofficial-cyanogenmod-12-1-t3120259/page22

Of course this kernel doesn't work with it, but it seems that the wifi disconnections are greatly reduced (wakelock time is half what used to be). Keep in mind this is VERY preliminary, as I tried it only for 2h or so.

Is it worth it to take a look at the wifi drivers included in its kernel?
[ONE Original Android Development] andip71:
I am quite boring these days, interactive.

And for the rest, I answered so many times the same already in this thread. Just search a bit.

No OC, no uv, touch boost slightly reduced. CPU max down to 1954 and gpu max down to 300.

Rest pretty much standard as I consider the default settings already quite good.

Andi
[ONE Original Android Development] andip71:
When I find some time, maybe next week, then I can have a quick look.

I still believe the wifi issues are more on rom side, less on kernel.

Andi
[ONE Original Android Development] gondsman:
I agree on that, also seeing as the issue is definitely not solved completely by the new driver. It seems to be better though.
[ONE Original Android Development] andip71:
And it is quite likely, they do not even have the drivers in their repo. Many times the prima drivers are not contained. Last example was the oxygen kernel repo.

Andi
[ONE Original Android Development] gondsman:
Well, if Sultanxda was able to use them in his rom, they are surely available somewhere... (worst case on his github). :)
[ONE Original Android Development] rahulrai:
Lord Boeffla has been doing so much for the community. & it's not mandatory. Don't talk rubbish.
[ONE Original Android Development] magnamentis:
you obviously also don't like learning to read, which as well is mandatory, how can you say such non-sense. nothing is mandatory, not even using the app at all is mandatory. but then again you'd have to read how to set up your kernel without. and then, since you're free to decide, there is no reason to write this here. it's rude and trolling even if true which it isn't.
[ONE Original Android Development] hp13:
i use similar settings but gpu is at 330. all running well on beta 18
[ONE Original Android Development] Rmaier14:
hi [MENTION=947981]Lord Boeffla[/MENTION], sorry but can you tell me, what version of your kernel i can flash with latest Euphoria 1.1 / 02062015.

thanks for answer, Rmaier14
[ONE Original Android Development] andip71:
I cannot, never use anything else than official CM for good.

But many here can, for sure. Guys?

(I would suspect latest CM12.1 beta kernel I provide should do)

Andi
[ONE Original Android Development] mp3deviant721:
Latest beta of the official and ZaneZam's unofficials works great.

OnePlus One | EuphoriaOS x Boeffla edition™
[ONE Original Android Development] Rmaier14:
which of them ?

thanks for answer, but which of them ?

Boeffla-Kernel for stock CM12s / Boeffla-Kernel for genuine CM12.1 / Boeffla-Kernel for genuine CM12 /

thanks. :confused:
[ONE Original Android Development] davebugyi:
12.1
[ONE Original Android Development] mp3deviant721:
12.1

Edit: davebugyi beat me to it. Lol

OnePlus One | EuphoriaOS x Boeffla edition™
[ONE Original Android Development] hp13:
just had SOD while running cm 12.1 beta 18 with similar to your settings except gpu is 330. I was using interactive and tripndroid . attached last kmsg and log cat.
[ONE Original Android Development] Pablo.x:
I flashed the lastest boeffla's beta for cm12.1 on the last euphoria's buid and sometimes when I try to unlock my phone, it stills in deep sleep, like if dt2w or power button didn't work.

It happened to me on other roms when I flashed kernels with different ramdisk.

I don't know if it's related now or not, but if someone has an idea... It will be great :)

Thanks in advance.
[ONE Original Android Development] anmar21:
I'm running exactly the same Euphoria OS plus latest beta kernel and no problem at all. Might be from your kernel settings...
[ONE Original Android Development] devilsshadow:
[MENTION=947981]Lord Boeffla[/MENTION] just wanted to let you know your kernel got me out of a pretty nasty bootloop situation on CM's 0606 nightly. I'll be running it for the foreseeable future so thanks for all your work.
[ONE Original Android Development] andip71:
I think he said... He solved a boot loop with the kernel. So all is good.

At least this is how I understood it.

Andi
[ONE Original Android Development] bernard134:
I'm on cm11s and in the Boeffla app I couldn't find tripndroid scheduler. Is it only available for cm12 and above?

Sent from my A0001
[ONE Original Android Development] nicolahaye:
Yes I believe its a recent change in the cm12 kernel only ;)
[ONE Original Android Development] andip71:
Yes, cm11s and cm11 kernels are end of development, so tripndroid is no more contained.

Andi
[ONE Original Android Development] devilsshadow:
Yes, that is indeed the case. Phone's been stable as a rock since last night, did a bit of stress testing and everything is right as rain so thank you again. And since franco pretty much dropped support for Bacon, your kernel is the only one I even considered running. I like a hands off, flash and forget approach to kernels and yours offers that.
[ONE Original Android Development] Fevves:
The question is: why cm11s is EOL? Many One+1 owners are still on that ver. so I can't figure out why cm11s does not deserve updates?

Just a rhetorical question, no pun meant and not intended to offend you [MENTION=947981]Lord Boeffla[/MENTION] as I indeed appreciate your hard work and constant support.
[ONE Original Android Development] maxver0:
A few. His sources are all up, you can grab it, can merge whatever you want.

Boeffla, I lost your e-mail with access code, can you sent me over new one? Check PM.
[ONE Original Android Development] Fevves:
Go figure... I'm no DEV and I really don't need replies like yours - you can't even know how many cm11s users are there just cause few are posting here, bur are willing to support the DEV (doing so) and are simply asking the question. If I wanted unofficial builds, I would go elsewhere.

I don't need replies like yours, as in - go compile your own.

[MENTION=5108269]maxver0[/MENTION] Thank you for not replying to my post anymore and thank you for understanding my POV.
[ONE Original Android Development] maxver0:
So you wanna start a fight. I do know, I'm one of the most active technical support users on reddit. I'm aware of users that wants to stay on kitkat, or want to go back. Well, looks like you do need unofficial builds, because he already answered that he will not support CM11, don't be a stubborn man.

So this thread doesn't need replies like yours.
[ONE Original Android Development] fmc000:
LOL
[ONE Original Android Development] andip71:
You can stop fighting.

It is simple: cm11 and cm11s are KitKat.

KitKat is dead, cm does not develop it anymore, oneplus do not, and also I am not using it anymore.

Hence, I dropped it too as I only develop what I personally use (see op).

But the kernel runs still fine and as a matter of fact cannot get outdated ever. Just will not receive new functionalities anymore, and no updates.

Time for KitKat is over, people should consider upgrading to lollipop. Or they need to stay on an old platform on own risk.

Andi