yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] kurtextrem:
May I ask which optimization patches were removed and which problems they caused? Not sure if I should upgrade, optimization always sounds like "higher perf" for me :D
[ONE Original Android Development] Almayce:
So any of u have the camera all choppy now? I'm asking because I heard there have been some camera commits added in kernel. I'm using to stock cm camera, gonna try others and edit later.
[ONE Original Android Development] andip71:
Yes, I do NOT have your issue.

Being on latest kernel and official CM12 nightly of yesterday.

I can lock the screen, unlock it and only 2 cores are running.

You _might_ have to wait for a Temasek Rom update again, I believe it has something to do with it...

Look here yourself:

https://github.com/andip71/boeffla-kernel-cm-bacon/commits/boeffla_v3_cm

The last 4 revert commits.

I took them over from my S3 kernels, so the might not be optimal for the OPO nor was I ever sure if they have any positive effect.

Think it is better to stay closer to stock with it.

Andi
[ONE Original Android Development] ek69:
[MENTION=2451647]molonad[/MENTION] Do you mean that all 4 cores are active ALL the time? Or right after when u hit power button to wake the phone all 4 are active for one second or so, then after it goes back to only 2 cores active?

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] andip71:
I can tell you, because I could reproduce it last Sunday still (when being on CM12 nightly of 18.01.).

You switched to 2 cores, and you saw 2 cores are only used.

Then you locked the phone with the power button.

Then you unlocked it again and the phone was using all 4 cores furtheron.

But I tried to debug this, before however I updated the rom to the latest nightly again, and it was gone... So I think latest nightlies fixed that again.

Of course I do not know how "old" Temasek beta6 is and if he updated to latest code base.

That's why it is like that. I cannot debug as I cannot reproduce. And I also do not want to go back to an old rom to debug as this is nonsense and waste of time...

Andi
[ONE Original Android Development] maxver0:
Blisspop 22,01, lastest kernel can't reproduce it either.
[ONE Original Android Development] DjDiabolik:
Yes... i thinks we need about this:
[ONE Original Android Development] ek69:
I just downloaded Jan 23 blisspop to try and if I choose zzmove, zzmove-moderate, "2 cores on" it activates CPU 0 and 3 for the most part, but when I lock and unlock the other CPU are on for a short while at the lock screen and shortly after unlocking.

The amount of time they are on varies a lot (at most a few seconds) but it does happen. That's why I asked how to reproduce and for clarification. I would say after that time period it looks like indeed only 2 cores are used for the most part, unless you do something CPU intensive like opening an app or browsing websites on chrome.

Just noting my observations and wondering if that's how it's supposed to be (which makes sense, 2 cores are used the majority of the time except when additional cores are needed, then they are plugged in) or is it strictly supposed to be "2 cores on" no matter what you do?

Cheers

(BTW this got me to try blisspop and it looks like a really nice ROM with lots of customization, just like temasek and how I like it :D )

Only thing left is untouched cm12 nightly but I am not sure if it will install with multirom.
[ONE Original Android Development] andip71:
But this is not how it should be.

2 cores means really 2 cores max. Never more.

As said, I can not reproduce it here currently. I also have not done anything in the new version, it just disappeared...

When it comes back to me, I will again look into it.

Cheers

Andi
[ONE Original Android Development] ek69:
Then it's definitely not working as intended with 2 cores max at any time for me. Plz don't take my posts in a negative way :) I don't want you to think I'm being rude.

I'll attach some pics to show what I see

- 1st is just in your config app while switching tabs

- 2nd is sitting idle at ak website (just cuz I know it's got a black background and it's easier to see)

- 3rd is when I reloaded the website

This is on both temasek 6.0 sabermod and Jan 23 blisspop.

If you are running stock cm12 nightly and you NEVER see more than 2 cores online with the config I posted, then something seems off with my installs. My temasek was a dirty flash so I thought maybe that's why, or like you said earlier that something isn't up to date, but the blisspop is a brand new install using multirom. And someone posted above saying they can't reproduce what I'm seeing lol

Now I'm wondering if multirom might be partly to blame lol. Just as I typed this post out I see multiple times other CPU cores flash on and off.

Again I'm not posting this in a negative way, so please don't take it that way, just posting what I'm observing :)

So far I'm really liking your kernel now that I've gotten more information about the internals from [MENTION=3279788]ZaneZam[/MENTION] :D

Cheers
[ONE Original Android Development] maxver0:
I just reproduced it on 23.01 blisspop. Looks like after unlocking device it turns on 3 cores always on, and 4th core show up in heavy task. Reproduction is 100% succesfully. I have uninstalled Device Control, so it can't be an issue. Also I'm running ZZMove Moderate. Interactive gov is affected too, haven't tried others.
[ONE Original Android Development] andip71:
No problem. I don't take that negative at all.

For the time being you need to live with it.

As long as I cannot reproduce it on a recent cm nightly, I cannot analyse.

Once it comes back I look at it.

Cheers

Andi
[ONE Original Android Development] matius44:
I think this is just miscommunication guys. ek69 said he chose "2 cores on" which is different than "2 cores". From my understanding, "2 cores on" means a minimum of 2 cores are always online but "2 cores" means maximum of 2 cores are used at all times. And that's how the kernel has always behaved with me with those 2 options.
[ONE Original Android Development] NickosD:
Quick question: anyone here with Spotify and having audio glitches? With ak I didn't had that much.

Sent from my bacon!!!!!
[ONE Original Android Development] molonad:
Right after I unlock phone, all 4 cores are active permanent ?
[ONE Original Android Development] andip71:
Can you send a screenshot of your Boeffla Config configuration of your hotplug profile please?

Thanks

Andi
[ONE Original Android Development] beany>:
I did, but changed to "2 cores" and it's gone. Although reading the last page of so "2 cores" should be maximum of two not minimum so now in not sure why it worked.

I could do with a script/tasker to change the settings.
[ONE Original Android Development] miguepereira77:
Excuse my ignorance, are u referring to "2 cores" or "2 cores on"? As there are two options. Thanks in advanced
[ONE Original Android Development] andip71:
Ok. You selected 2 cores on... This means not 2 cores max!

It means 2 cores always in, but can also be 3 or 4... So in your case all is correct.

Andi
[ONE Original Android Development] andip71:
"2 cores on" means: 2 cores are always on. Can be 2, 3 or 4.

"2 cores" means 2 cores max. So can be 1 or 2 cores but not more.

Just to explain again...

Andi
[ONE Original Android Development] ZaneZam:
And I have to add if zzmoove native hotplug is used then the "all cores online" after coming from suspend is intended and per design just to let u know ;)
[ONE Original Android Development] ek69:
Just tried with both options, they both produce the same result (need a banghead emoji in Tapatalk lol)

//edit

When I go 1 core, it seems to have all 4 stuck on, which sounds like the issue that other guy posted about with 2 core (after locking then unlocking the screen, they all stay on)

Sent From Lollipopified Bacon Goodness!
[ONE Original Android Development] miguepereira77:
Yes, I know, that's why I asked, because I was confused, as I think he meant "2 cores on" and not "2 cores" in reference to the audio glitches I mean...

Edit: BTW, I know is CM's bug and not kernel related, just trying to find some kind of workaround as this bug is really annoying...
[ONE Original Android Development] ek69:
Delete
[ONE Original Android Development] maxver0:
That's true. And happens in my case too. I'm using zzmove native hotplug so I dont mind but it might be an issue for other users who actually uses it. I clean flashed(data stays) blisspop as in his guide.

http://xdaforums.com/oneplus-one/de...-team-bliss-bacon-10-28-t2921057/post58393664

Also this did not happened on previous build, 22.01. So most likely it's rom related, but why, it shouldn't affect hotplugging I think.
[ONE Original Android Development] NickosD:
With 1 core, before locking the phone only 1 stays active, after that all are.

But I use bliss 20 Jan.

Sent from my bacon!!!!!
[ONE Original Android Development] andip71:
As said, and with that I close the topic for now:

I don't have it. Cannot replicate.

Hence nothing to analyse or fix.

And if someone has this on official cm nightly, please let me know as this is my one and only reference.

Once I have it, I can do something about it.

Andi
[ONE Original Android Development] andip71:
Everything is possible. As mpdecision does the hotplugging and comes with the rom...

Maybe I move the hotplugging check to a level lower one day, but not yet sure.

Andi
[ONE Original Android Development] NickosD:
Keeps happening at 23/01 bliss. I use zzmoove native anyway which it works fine.

Sent from my bacon!!!!!
[ONE Original Android Development] waterdaan:
If you don't mind

Can you tell me what app or widget you use to show the CPU and temperature like that

Thanks!
[ONE Original Android Development] hhp_211:
It's just in developer options,, show cpu info
[ONE Original Android Development] lchiocca:
Andi, from what i see, a lot of people are confused by the actual label "2 core" vs. "2 core on". Would it make sense to rename the labels to make them less ambiguous? E.g. "min 2 core" or "2 core (min)" vs "max 2 core" resp "2 core (max)"?
[ONE Original Android Development] andip71:
Indeed, thinking about it already for next kernel version. Just people must then reconfigure this again in the app. Should not be a biggie though...

Andi
[ONE Original Android Development] duke_mac_l:
Can you please upload the cm11 firmware again or send me a link via PM. Because the link you posted is not available.
[ONE Original Android Development] tobitege:
Sure, here it is: https://mega.co.nz/#!iAlzGTQJ!WfxRiJVhA9Q-H_6AKD1tt4eEhf4VEEXlBsT22UpjpII

Also fixed the link in my original post, forgot about copy/paste link shortening...
[ONE Original Android Development] andip71:
... Or just look in my downloads for modems... The one's labelled "full..." also come with the surrounding firmware contained and flashed.

So, the full 44s modem would bring you back to cm11 basis too.

Andi

Andi
[ONE Original Android Development] tobitege:
Andi, are the big differences between CM11S and CM11 nightly firmware or modem (if at all)? Just curious, Danke. :)
[ONE Original Android Development] andip71:
Between cm11 and cm11s only the modem part is different.
[ONE Original Android Development] andip71:
All... I was finally able to reproduce the max core problem again, and maybe we have a pointer (ZaneZam and me...).

If you are not using zzmoove, switch to the governor you want, set hotplugging profile as you want and reboot...

It should then work as long as you don't load zzmoove again.

So far my findings...

Andi
[ONE Original Android Development] suaverc118:
Excuse me if I missed it but was the power save gov removed? First time I've never seen it.
[ONE Original Android Development] andip71:
No, was never removed by me.

Andi
[ONE Original Android Development] molonad:
Yes, I was wrong 3 cores are permanent online when unlocked
[ONE Original Android Development] molonad:
But it's okay I will configure cores in tuneables, not big deal for me, next temasek version will probably fix it ☺
[ONE Original Android Development] Stylo King:
Seems like I have the worst luck compared to each one of you.

You people are lucky running custom kernels, But I have problems one after another.

1. Tried AK kernel, Like that very much but apps like Facebook and Chrome were lagging heavily.

2. Switched to Boeffla Kernel, The best one so far but my device freezes sometimes when I turn off screen and I can't wake it up and it reboots automatically after sometimes.

3. Finally tried Franco Kernel, The audio glitch was totally gone, Performance was good, Everything was smooth but the battery life was reduced heavily.

I don't know what is the problem, Its just I think I have the worst luck.

Currently on stock kernel.

Rom - Temasek 6.0 Sabermod.

Sent from Temasek's Lollipopified Bacon
[ONE Original Android Development] maxver0:
Are you using stock kernel setting?
[ONE Original Android Development] Stylo King:
yes.. no options except stock now

Sent from Temasek's Lollipopified Bacon
[ONE Original Android Development] andip71:
No, I think only next zzmoove version will fix it finally.

ZaneZam and me were doing analysis today. And it seems to be a side effect of zzmoove in last version.

As I said before, we now have a pointer and Zane is already working on fixing it.

However, if you do not use zzmoove, it should fully work for you. You just need to configure everything and reboot. And not to switch to zzmoove, even not for a test, as this will bring the effect back.

Well, I do not want to make someones work bad, but maybe you should at least once try official CM12 nightly. Yes, it is not compiled with Sabermod, it does not have all sort of fancy tweaks, but it runs absolutely 100% rock stable for me with my kernel. Not a single reboot or anything in the past weeks with it.

Just my 5 pence...

Andi
[ONE Original Android Development] ivan0909:
What Kernel I should use in AOSP roms? Like Líquid 5.0...
[ONE Original Android Development] pa.pn2:
Why not this? Works perfectly..
[ONE Original Android Development] Mrj0to:
Hi guys. I'm having this battery eating issue..

Android system is competing with my SOT in my battery stats. Does anyone know how to prevent this?

I can't block wake-ups in privacy guard from Google services because they are not displayed there.

Sorry can't provide any wakelocks yet as I have forgotten to install BBS as system app after my rom update.
[ONE Original Android Development] ivan0909:
Yeah, but what versión CM11, CM12... ROM AOSP
[ONE Original Android Development] pa.pn2:
Depends on ur rom. If lolipop choose a cm12 kernel. For kitkat the cm11 kernel
[ONE Original Android Development] ivan0909:
If is Lollipop, (CM12 or AOSP), i should install CM12 Boeflla
[ONE Original Android Development] andrea90:
Wakelocks on 2.1, I'm trying again 2.0 and seeing...
[ONE Original Android Development] Stylo King:
Yes sir, Will flash the CM12 Nightly with your kernel.

Thanks for your reply.

Sent from Temasek's Lollipopified Bacon
[ONE Original Android Development] suaverc118:
I'm using the SM version of the latest kernel. I assumed it was based off of yours. Am I missing something?? Here is a pic of the govs.
[ONE Original Android Development] andip71:
The sabermod version ZaneZam creates is 100% using my repo, yes.

And looking at your screenshot, all seems to be fine. What are you missing?

Cheers

Andi
[ONE Original Android Development] andip71:
What kind of wake locks? Kernel or partial wake locks? If so, coming from what sources?

CM11 or CM11s kernel?

For CM11s and CM11, almost nothing has changed between 2.0 and 2.1, for sure nothing that could create additional wake locks.

Andi
[ONE Original Android Development] suaverc118:
Missing power saver
[ONE Original Android Development] andip71:
Indeed, the powersave governor is still in the kernel. But it is hidden by the app as I do consider this governor to be completely useless for an Android device.

Powersave Governor:

The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.

This behaviour can be achieved without a new governor by just minimizing max CPU freq down to the minimum. So this governor is not required in my opinion.

Andi
[ONE Original Android Development] :
and conservative?
[ONE Original Android Development] andip71:
Conservative is a "real" governor that does useful stuff. So conservative is of course in.

Also shown in the screenshot above, first governor.

Andi
[ONE Original Android Development] :
can you add for gpu? :)
[ONE Original Android Development] andip71:
Ok, you are jumping topics now. I talked about CPU so far.

GPU conservative... Well, I will for sure not try to port myself. If you know a kernel that has it, let me know and I try to pick that. Do you know any?

Andi
[ONE Original Android Development] :
ak used to have it but it disappeared, was tested in beginning in the profile thread as pretty energy efficient. I fid get more sot I think. havent seen it since cause it dissapeared
[ONE Original Android Development] andip71:
Well, then the real question is - why did it disappear? AK had for sure a good reason for it...

Andi
[ONE Original Android Development] :
probably he never said why, did ask though

should you stumble across it :)

your kernel is already perfect ofcourse, thank you for that

edit Franco used myfluxis :) way back

http://xdaforums.com/showpost.php?p=53856030&postcount=53
[ONE Original Android Development] tobitege:
[MENTION=5461670]bachera[/MENTION]: don't get me wrong, but it doesn't make sense to throw around a lot of ideas and fancy governor names if there's no info attached to their benefits and use-cases. ;)
[ONE Original Android Development] maxver0:
Stop using phone. Turning it off would do best.
[ONE Original Android Development] andrea90:
Cm11s 2.1

i'm sorry but I can't help you more because I needed a good battery life so I returned to 2.0. Now all is perfect, no wakelocks
[ONE Original Android Development] andip71:
At least I cannot see in any of the repos a version of a conservative GPU governor. Either they all removed it again for some good reason or... yeah, would be interesting why.

No problem. I checked again and I did not see anything in the changes that would cause more wake locks. Also quickly checking my betterbatterystats lock, nothing changed here.

So don't know why it is different for you. But as we all know... not everything is equally good or bad for everyone. So if you are happy with 2.0, keep on using it.

Andi
[ONE Original Android Development] andip71:
Yep, I now have the answer for you.

The reason why all removed the conservative GPU governor again was:

CM team introduced a backport of the devfreq part:

"devfreq: Backport MSM devfreq features from 3.10"

This change did break the conservative GPU governor and subsequently it was not available anymore in the kernels.

Andi
[ONE Original Android Development] andrea90:
[MENTION=947981]Lord Boeffla[/MENTION]

I had same problems like this guy, I hope it could help you ;)

p.s. Thank you so much for your work, your kernel is a masterpiece!
[ONE Original Android Development] :
hope they can fix I love conservative gpu
[ONE Original Android Development] andip71:
Android system is a bunch of services in the rom (as you can see even in the list of processes posted).

Not something I can influence from kernel side. It is like it is.

Especially when you have not a lot screen on time, it is quite normal "Android system" climbs up to #1 as all it's services still need to do their work.

Well, it is not about fixing, it is about porting the conservative governor to 3.10 devfreq.

Maybe someone has the time and motivation for it :)

Andi
[ONE Original Android Development] :
thanks for finding it.

use case would be extremely power efficient based on results on cm11. I had over hour screen off time, plus ultra low power some how with screen off stuff. That was in September. Other sources would be found by reading synapse profile thread. A lot of people recommended that in their profiles.

I am not sure but somehow it influenced listening to music. With about 1-2% drain. That drain increased after that commit then I think but I have no clue on how they are related. Battery drain after and on lp has been high for me ever since. Dont know why.

I checked sources but couldnt find anything and haven't the faintest idea on how to port it.
[ONE Original Android Development] real_pac:
[MENTION=1470009]boeff[/MENTION]la Absolut gute Arbeit herzlichen Dank! Since I use your kernel I got the stability of cm11s but the great performance from lollipop! I made my on settings and I can't say nothing else then awesome! Great battery smoothness reaction with low settings

Schöne Grüße aus Österreich :)
[ONE Original Android Development] andip71:
Thanks a lot, always enjoy also good feedback between the usual problem reports which are the majority by nature.

Viele Grüße zurück von einem Bayern nach Österreich ☺

Andi
[ONE Original Android Development] Goggle81:
I also will bring some good feedback to the thread.

Great work Andi! I really appreciate your efforts and your friendly support.

Grüße aus Franken ?
[ONE Original Android Development] ReAnimat:
5CE68301GF695502V :beer:

Ein kleines Bier für die Arbeit. keep up your great work ! :thumbup:
[ONE Original Android Development] real_pac:
Näher als man dachte :)

So I read your description on your homepage about the scripts from s3 kernel. Are there some new or adapted scripts for opo too?

I bought the donation app so I'm gonna test the pro futures soon. Is there also a build prop editor in your app like device control for example to change vm cache size and other stuff?

What do you think about row 256 reading setting? Should I go up about 512?

Thank you very much Andi!

Schöne Grüße

Tim
[ONE Original Android Development] maxver0:
1024
[ONE Original Android Development] real_pac:
Why would you prefer 1024? I ran a speed test for internal memory
[ONE Original Android Development] maxver0:
How was it?

It's not a test for our memory but by looking at the theory of readahead buffer and all other performance tests (on the internet) I find that we should stick above 1024. I don't think default readahead buffer was chosen randomly.
[ONE Original Android Development] andip71:
Hi Tim,

not entirely which scripts you mean. If you could let me know what it is (or do you mean the tweaks section?) then I can answer.

There is no build.prop editor in my app. The Boeffla-Config App is an app to control the kernel only. build.prop however is a file coming with the rom.

My philosophy is to not mix up these two things and have the kernel config app only deal with kernel aspects (one exception only is the wifi scan interval configurable, but also only this does not affect build.prop). So my app will never access build.prop ever.

I think 1024 is a good compromise for readahead for the average user.

Depending on quality of your nand, it can of course be better with slightly higher or lower settings. Finally if you want to have the absolute maximum, you would need to test and find out for your specific device yourself.

It is a good average setting which should fit almost everyone.

Andi
[ONE Original Android Development] MortenHeck:
Not sure if this is kernel related, but when I use the Boeffla Kernel on the latest Validus Rom for One+, my phone app is chrashing when I am trying to make a call. I did a clean install, flashed the kernel after I installed the Rom. When I flash the ROM with stock kernel, everything works perfect. Any solutions?
[ONE Original Android Development] Pablo.x:
Maybe is modem related, do you have the latest one installed?
[ONE Original Android Development] andip71:
No solution from my side.

Just a slightly sarcastic side comment (sorry, which I cannot hold back for good reasons): I definitely know why I am NOT using any other roms instead of CM12 official nightly.

Whenever I read these kind of issues, it is always on "custom roms", never have any of them on latest CM12 nightlies.

Maybe worth considering for the people that want to have stable phones.

No offence, just my honest and personal opinion.

Andi
[ONE Original Android Development] MortenHeck:
Yup, everything is up to date!