yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] tobitege:
[MENTION=947981]Lord Boeffla[/MENTION] your post just made my day! rofl
[ONE Original Android Development] MortenHeck:
Non taken, but it is annoying, I really like this kernel!
[ONE Original Android Development] maxver0:
It's rom issue.
[ONE Original Android Development] NickosD:
Dirty flashed your rom? If yes, try a clean flash.

Sent from my bacon!!!!!
[ONE Original Android Development] chineel:
May Be theme related Issue
[ONE Original Android Development] andip71:
Allright guys,

bigger update to CM12 kernel in pipeline... I just started some testing and finetuning.

New zzmoove will finally fix all the issues reported by people with the hotplug profiles (also for non-zzmoove governors, as this was a side effect...). Also additional zzmoove native hotplug modes included (all credits to Mr. ZaneZam).

Toolchain likely lifted up to gcc 4.8 (instead of 4.7) if it runs stable for me in the next hours.

Hotplug profile names reworked to be more clear.

All latest CM patches included, ramdisk updated, internal su updated, minor internal compatibility optimisation...

So, stay tuned.
[ONE Original Android Development] real_pac:
Thanks my bad sorry I'm using Swift key with 3 languages and my phone language is set to German. Many times before I recognized that the most auf us pend between 512 1024 sometimes 1536 I'm using currently 256 and everything is good. I know it didn't make a big difference.

---------- Post added at 10:52 AM ---------- Previous post was at 10:44 AM ----------

Hey Andi, thank you very much!

I looking for my own ultimate setting like I did it before on my last love Lg G2 :)

That's also true. It isn't necessary. There are many other apps for build prop if we want to edit. I thought maybe you planned it for the future builds hehe :)

Exactly I meant the scripts on tweak section. I saw the description on your homepage. You recommend to turn off on OPO or to use not every script.

My readahead was usually on 1024 I thought I will give a try to 256. Is it possible that this small change could make a big difference?

Thanks for your detailed support

Schöne Grüße :)

Tim
[ONE Original Android Development] tobitege:
[MENTION=3113956]real_pac[/MENTION]: from my experience with multiple devices/roms in the past, 1024 should be fine, but going down to 256 will almost certainly have a noticable, negative effect. I don't see a technical reason to limit it that low.
[ONE Original Android Development] real_pac:
Thanks Bro! I'm not sure but I read somewhere else that some say 256 for newer phones 512 is absolutely enough. I thought I'll give a try. Now I'm on 1024 and won't change it :)
[ONE Original Android Development] molonad:
Yes, iam really looking forward for next version
[ONE Original Android Development] andip71:
Yep, especially as your issue with the cores should be fixed in it :)

Andi
[ONE Original Android Development] molonad:
Hi when i for example change readhead to 256 kB will it be battery friendly or is it same as on 3000 kB? Thanx
[ONE Original Android Development] magnamentis:
yeah it's the old story about how many things have to be in sync. i mean cm makes changes, kernel dev updates his kernel to the changes when relevant and done, while custom roms based on cm can be way behind in updating sometimes and if it's only 1 or two days, you already are out of sync.

there is a solution, quite easy, just takes a bit of reading and patience: check your rom updates changelog ( mostly the date is sufficient ) and the last kernel update changelog ( or date ) and if the kernel was updated but your preferred rom wasn't you just have to restrain yourself from flashing away with the kernel until it does. same applies the other way around, just the kernel devs are mostly much quicker to avoid trouble.

EDIT: that's basically the problem with other kernels, they have more things to keep in sync like third party tweaking app and/or UKM which would make 5 in case of custom rom based on cm12 and 4 in case of original cm12, still way too much to handle, results can be seen (read)
[ONE Original Android Development] MortenHeck:
Thanks for a informative reply, really appreciate it! :)
[ONE Original Android Development] Hana88:
But the zanezam is fixed for cm11s too?
[ONE Original Android Development] ZaneZam:
Yes I'm fixed for cm11s too :D

No seriously you mean if zzmoove is fixed for cm11s, yes I think Lord boeffla will release a new version for all variants so it will be fixed there too
[ONE Original Android Development] andip71:
Yes, but I plan to push CM12 kernel out today.

And cm11s / cm11 kernels maybe tomorrow (I just upstreamed them for a test and want to see how that goes first).

Andi
[ONE Original Android Development] Hana88:
You have more love for cm12 user than US :(

:p

I can wait for cm11s kernel <3
[ONE Original Android Development] andip71:
Well, CM12 is the future. CM11(s) will be dying over the time.

But could be, I will not release any kernel today. Just found a glitch where I need either a dirty hack or a brilliant idea by Zane :)

Let's see how and how fast.

Andi
[ONE Original Android Development] waterdaan:
event wakelock

I'm getting some kernel wakelocks

Event0-908

Event2-908

Event3-908

I thought it might have something to do with the swipe buttons to sleep feature, so I disabled that, but I'm still getting that wakelock.

I'm using the CM11S 2.1 kernel

Should I go back to 2.0?

I don't think I had these wakelocks when I used that version
[ONE Original Android Development] andip71:
You can try.

But I don't think it will make a difference. It would highly surprise me.

Between 2.0 and 2.1, only 4 commits were reverted back which were from the S3 kernel initially, to be even more close back to stock.

So I highly doubt.

But yeah, try it and let us know.

BTW - where did you see this wakelocks, what % of time did they consume etc?

I have never seen them on my cm11s driven device here.

Andi
[ONE Original Android Development] andip71:
Ok, we have worked out a solution for this.

Hence, I will soon first release a new Boeffla-Config App, and the CM12 kernel version 3.0-beta7 will follow.

Andi
[ONE Original Android Development] kalpik:
Waiting eagerly ?

Sent from my A0001
[ONE Original Android Development] andip71:
Step 1 done. New app 2.1.66 is available.

Now packing the kernel together, creating change log...
[ONE Original Android Development] andip71:
Beta7 for CM12...

Hi all,

ok, finally here we go - 3.0-beta7 for CM12 arrived.

Version 3.0-beta7

27.01.2015

Updated with latest 7 CM kernel commits for CM12 until 27.01.15 (-> 1e6687b)

zzmoove governor updated to 1.0-beta6 (credits to ZaneZam) - together with the new Boeffla-Config App 2.1.66, the reported issues with hotplugging profiles (core limitations were not respected after zzmoove was used) should now be fixed

Introduce additional native hotplugging profiles for zzmoove (credits to ZaneZam)

Names for hotplug profiles changed for better clarity (adjust to your profile again after flashing the kernel !!)

Internal su updated to version 2.45

Ramdisk updated to official nightly of of 27.01.15

Minor internal improvements

Toolchain changed to CM12 standard toolchain gcc arm-eabi-4.8

Enjoy

Andi
[ONE Original Android Development] NickosD:
Max cores works great with zzmoove and zzmoove Max 2 cores hot plug. ?

Sent from my bacon!!!!!
[ONE Original Android Development] tobitege:
Installed updated kernel app and flashed beta7... all working perfectly again! Thank you so much!
[ONE Original Android Development] maxver0:
My body is ready. :angel:
[ONE Original Android Development] andip71:
Need soon some pre-testers...

Hi all,

finally I had nothing better to do today (hehe), so I decided to put the upstream to Linux kernel version 3.4.105 into all my three kernels (cm11, cm11s and cm12).

As this changes lots of code, I see it currently as an experimental change and would like some more eyes looking on it before this is something for the public.

Saying that, I will be looking for a few testers from probably tomorrow onwards for all the three kernel variants. The testers should be brave and ready to accept weird effects (although had not any so far with the already upstreamed kernels).

If you are interested, stay tuned until I let you know... :)

Andi
[ONE Original Android Development] molonad:
Thanx boeffla, its awesome, all i missed is here! Great! Please what is for example diference between 2 cores max and zzmove native 2 cores max, which is more battery friendly? Thanx
[ONE Original Android Development] andip71:
In first case, standard mpdecision is handling the hotplugging.

In the last case, zzmoove takes care of the hotplugging itself (mpdecision is disabled for hotplugging in that case).

Which one is more battery friendly... time will tell. My strong feeling is, zzmoove native hotplugging is more trimmed to save battery. So I guess the native hotplugging by zzmoove should do fine.

But let's the master of zzmoove add his opinion too [MENTION=3279788]ZaneZam[/MENTION] :)

Cheers

Andi
[ONE Original Android Development] lchiocca:
And i thought the new names were disambiguous :)
[ONE Original Android Development] maxver0:
Too bad I need stable phone very day for work :crying:
[ONE Original Android Development] andip71:
I think the new names should be pretty clear now.

However, the question here was the difference between native zzmoove hotplugging and general hotplugging (by mpdecision).

So, would say that was a fair question which deserved a good answer.

Cheers

Andi
[ONE Original Android Development] andip71:
Hehehe. Come on.... no risk no fun. Be brave, be bolt :)

No, honestly if you are dependent on your phone, you might not join this pre-testing of the upstreamed kernel.

Honestly I do not expect bigger issues, especially as my two phones run quite fine for a few hours already with it. But... you never know.

Are you on cm11s or cm11, or cm12?

Andi
[ONE Original Android Development] _Beni_:
I also could play tester, two things must at least work: Spotify and no sound while school :D (Currently Spotify is not working well, only zzmoove - optimal - 2 cores min - 422Mhz min seems to work)
[ONE Original Android Development] spanish33:
I can test cm12 version for you but I am using SlimLP so I am not sure if you only want testers who use cm
[ONE Original Android Development] molonad:
And one thing iam missing, for example 2 cores max, but both of them on, i need this for listening music, there is bug on temasek that I must use two cores on bigger frequency in screen off, if i Will use only one core it shutter and its lagging, but for now iam just using zzmove 2 cores min and in tuneables i turn off another two cores
[ONE Original Android Development] Fenvarien:
I'd be honored to be a tester for you [MENTION=947981]Lord Boeffla[/MENTION] :) Currently I'm on Euphoria ROM.
[ONE Original Android Development] ZaneZam:
yeah this beast takes over then yes *g* but as shown again today first it has to be put in its place :D

good teamwork again my lord ! :highfive:

and about if its more battery friendly: well that's still a good question and i guess that might be really answered by many others then us with constantly and significant

changing systems :) personally i cant say it atm. and i will not figure it out soon as i'm already working on the next version and testing starts all over again :)

speaking of testing: if u more advanced guys out there want to try out some of the new features which where introduced in this feature preview-version 1.0 beta6

then feel free to play araound in "tuneable mode"! for the time beeing i can suggest some settings which might bring us more responiveness and a more

fluid experience during handling (respectively touching the screen or using the hardware buttons)

if u enable and setup the "native touchbooster" by giving the tuneable inputbooster_cycles a value of 10 and enable inputboost_punch_on_fingerdown by giving it the value 1

then u should start to feel some speed differences in general if u touch the screen. if u in addition give the tuneable

inputboost_typingbooster_cores the value of 3 u will get (beside of other boosts) 3 cores online if u are typing on the device. ;)

that's just a little bit of info about one new feature. ehm before more questions are coming up i have to state that i can't answer them 100% atm

first because of less time (hence this preview version -> i "had to" bring out this hotplug fix in the middle of merging stuff *g*)

and second as i'm still working on it :) but things are stable and all the new features are working so far... i think... i hope.. :) btw. kudos and all credits to [MENTION=349360]ffolkes[/MENTION] for them!!

however they will come to a finished and good testet state in next version. ah and btw none of the new features are enabled per default so if u do not want to use

them u will not see hear or smell them and don't have to care about what i wrote here :)

ok but now have fun with it.... :fingers-crossed:
[ONE Original Android Development] spanish33:
Thanks [MENTION=3279788]ZaneZam[/MENTION] for your suggestions will test it for a couple days and see how it works.
[ONE Original Android Development] chineel:
I am ready to test that on my CM 12 Build
[ONE Original Android Development] waterdaan:
Thanks for your quick response!

Could I have caused this problem by flashing cm12 and then coming back to cm11s and only flashing the modem.bin without the other files, e.g. static_nvbk.bin?
[ONE Original Android Development] magnamentis:
you have to flash the firmware, the modem is not the main point here (and therefore not sufficient), usually (not guaranteed though) modems are compatible cross api and roms but the firmware in this case is not, mostly related to proximity sensor handling, it's somehow reversed as from cm12 compared to cm11 and cm11s
[ONE Original Android Development] maxver0:
Great, now I have to donate.

---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------

5PR656809M5653119 :eek:
[ONE Original Android Development] andip71:
Meanwhile the concept is very sophisticated, so that would be a new profile and easily doable.

With the framework in place a piece of cake.

Will try it out tomorrow...

Yes, might be. As Magnamentis explained already, firmware is indeed the key point with cm12 vs cm11 these days.

Thanks a lot. So much appreciated.

Cheers

Andi
[ONE Original Android Development] waterdaan:
Noob here!

What is the firmware that you mention?

I just flashed, see screenshot, does that include the firmware?

Thanks :)
[ONE Original Android Development] andip71:
Yes, in my full modems the firmwares are included.

Andi
[ONE Original Android Development] magnamentis:
yes, you're good to go with this one :)

ninjad with the boss hehe.....

BTW [MENTION=947981]Lord Boeffla[/MENTION] _ since i'm already at it, i'm using 3 roms with your kernel CM12 _ BLISSPOP _ CM11 just in case need more testes, you've got my email
[ONE Original Android Development] tobitege:
...add to that Temasek, Resurrection Remix, SlimSaber and Euphoria as working perfectly with beta6/7 :cowboy:
[ONE Original Android Development] acidburn94:
Hi lord boeffla, i saw you have upgraded the hotplug, and i'd like to know which is the best profilo according to you forma battery life without deleting performance, something like zzmove optimal for CPU!:)

Thanks in advanced
[ONE Original Android Development] abhibnl:
Consider me in for cm11s testing! ???

Sent from OnePlus One Powered by Boeffla
[ONE Original Android Development] poondog:
Hi sir, sorry to bring this up from yesterday but what app did you use to test this :)
[ONE Original Android Development] waterdaan:
Thanks!

It's working well now
[ONE Original Android Development] kipue:
By the way, total OT:

How should one pronounce the name of your kernel?

Beef-la

Bo-fla

Beu-fla

...?

Ahah, might sound a strange question, but I work in the field of language and this is the kind of question I also ask myself all the time :)

Love your work by the way, thanks for it ^^
[ONE Original Android Development] andip71:
Good to know. It seems, the firmware has much bigger side impacts than many of us (including me) did know.

Ha, nice question. Reading through your suggestions, I would say the Beu-fla is the best fitting.

The word itself comes out of the French language (as far as I know). I think the dish there is called beuf-a-la-mode (sorry, my French language skills are extremely limited).

On my homepage in the FAQ you can find why the kernel has this weird name at all :)

Cheers

Andi
[ONE Original Android Development] kipue:
Oh, great :) I'm French so that's why I thought of this pronounciation, but I did not think of checking the FAQ for this answer.

So, that's clear now, and yes then you are right to say it this way.

Now I can safely tell my wife :

-Today, dear, I switch to Boefla Kernel!

and she'll still reply:

- That's nice, what's a kernel?

But at least, i will have said it right :p
[ONE Original Android Development] maxver0:
Found it on Internet. I think that it was simple app to test speed and then someone made this summary table.
[ONE Original Android Development] andip71:
Update: The pre-testers that appointed themselves yesterday just got links to the upstreamed test kernels.

Let's see what they say :)

Andi
[ONE Original Android Development] tobitege:
Andi, can I jump onto your fast-moving beta train as well, please? :)
[ONE Original Android Development] maxver0:
Cho choooo!

---------- Post added at 09:41 AM ---------- Previous post was at 09:41 AM ----------

How about my app code ;)
[ONE Original Android Development] andip71:
Sure, you will have a PM soon.

Was sent already yesterday. Gmail tends to assign it to wrong categories like Spam or Travel. Can you please check again=

Andi
[ONE Original Android Development] maxver0:
I forgot i use different email for PayPal :eek: It was in spam folder tho.
[ONE Original Android Development] andip71:
Yep, I thought so :)

If you want the code being generated for a different mail address, just PM me the address. I can do that for you too.

Andi
[ONE Original Android Development] maxver0:
No need, activated already.
[ONE Original Android Development] maxver0:
I'm running test version. Can you adjust your app to don't display previous version as new update? It pops up every time I open app
[ONE Original Android Development] andip71:
Well, you can switch this notification off in the the app settings.

Generally I am not looking into putting specific logic in the app for that.

That is the "downside" of being a pre-tester unfortunately.

Your gift for being able to test earlier than others ;)

Andi
[ONE Original Android Development] Fenvarien:
[MENTION=947981]Lord Boeffla[/MENTION] Quick feedback after some hours of test drive with beta8: All systems functioning within normal parameters. :) Very stable, no side effects or other hiccups. The new hotplug modes are working very well too.
[ONE Original Android Development] andip71:
Thanks, this is in-line with my experiences on both cm11s and cm12 since yesterday so far.

Andi
[ONE Original Android Development] magnamentis:
spam folder has to be considered a second inbox nowadays even all email form google themeselves they're unloading into my spam folder :) checking the spam folder became a routine though, very much recommended if it does or can cost something to miss emails
[ONE Original Android Development] andip71:
Sadly, very true.

And also a reason I am not using my googlemail account for important things anymore...

Andi
[ONE Original Android Development] magnamentis:
running testkernel on cm11, as expected nothing found neither good or bad. any hints what to look at, meaning is there any specific testing (test runs) which can be done to tease the kernel a bit to it's limits, so to eventually find something that might be intermittent in daily use?
[ONE Original Android Development] andip71:
Well, as you know my opinion about Linux upstreaming: I think it does not change anything obvious. Many changes in the upstreamed Linux kernels do even not have any effect in Android kernels as they are not used.

I nevertheless did it as it was rather simple + I found some time + for some it is an important "marketing info" (which I typically do not really care about).

So.. no, nothing specific to look at. If all works as good as before, I would be quite happy. And I think, this is the case.

Cheers

Andi
[ONE Original Android Development] magnamentis:
it is working as good as before, so glad to know someone being happy hehe... however will move to blisspop later today and verify the same expected result :) :good::highfive:
[ONE Original Android Development] hhp_211:
[MENTION=947981]Lord Boeffla[/MENTION]

If it's not to late I would love to be on your kernel testing list :o
[ONE Original Android Development] andip71:
It is BY FAR too late, man.

Hehe, kidding... :)

You have a PM.

Andi
[ONE Original Android Development] andip71:
All pre-testers can test another update

Hi to all pre-testers of the upstreamed versions!!!

I just uploaded new versions (same file, same location as before) for you where I on top updated the kernel internal busybox to latest version 1.23.1 again (self-compiled from sources, as always).

So if you re-download the kernel again, you can implicitely also test this.

I have not come across anything bad so far, so the busybox seems to work fine. But this is quite crucial, I ran many times into busybox issues in the past before I compiled it myself.

Andi
[ONE Original Android Development] tobitege:
Perfect timing, just 2 minutes ago I got the previous beta8 flashed... onto next build then. :D
[ONE Original Android Development] andip71:
You don't need to.

Just this version is now likely to become the next public version, if all is well :)

Andi
[ONE Original Android Development] tobitege:
No problem, Andi.

But there's now way for me to directly test the kernel's busybox since I'm a Linux noob? ;)
[ONE Original Android Development] andip71:
Well, you can enter the command "busybox" in a terminal window and will see, the version climbed up to 1.23.1.

However this is not a real test and therefore quite useless.

But no, busybox is used internally by the kernel during startup and also in the interaction with the app.

If you can change settings, if they apply during bootup, etc etc.. then all is good.

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

The new test build works just perfect, all changes in the app are applied and sticky after a reboot.
[ONE Original Android Development] acuicultor:
Amazing battery life and performance with cm12 and Boeffla b7. Thanks Andi.
[ONE Original Android Development] shadow47:
Your config?
[ONE Original Android Development] acuicultor:
Zzmove batery yank(268/2457), zen, 1024 readahead, zz native hotplug, sync on, brightness auto,no uv, the rest is zanezam and lord's magic.Thats all
[ONE Original Android Development] shadow47:
Thanks I will test it.
[ONE Original Android Development] chineel:
Mine too test kernel working Very well since morning I am testing My new build with New Kernel and Working very smooth and stable. Better than beta 7 updated latest one also. Sorry for very late posting Busy supporting Linux in my local area along with new ROM compilation for Nexus 4
[ONE Original Android Development] suaverc118:
Can't wait to try the new kernel.
[ONE Original Android Development] real_pac:
Hey Andi thinks for the new build. I read that some of us have the Spotify bug also with new release. I tried all hotplug settings but the glitches are more then beta 6. Could I try maybe something different to eliminate the glitches?

Thank your very much

Lg
[ONE Original Android Development] andip71:
Not I could help here, maybe others can kick in.

I never used Spotify ever (and have no plans to change that any time).

Andi
[ONE Original Android Development] real_pac:
I meant thanks not thinks. :) I hope cm will fix this as soon as possible...

Tim