yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] magnamentis:
that's a no ?

you contradict yourself you say yes and then name the wrong version it's 7a not 7 you need
[ONE Original Android Development] BrunoNRG:
I posted the name of the latest file / kernel that can be downloaded here http://boeffla.df-kunde.de/bacon/boeffla-kernel-cms/cm11.0s_download/Test/Series 2.x (for XNPH38R)/, I only installed it this morning, it only says beta 7, not a or b
[ONE Original Android Development] cerealguy:
Download 7a version!!!
[ONE Original Android Development] BrunoNRG:
Can you please tell me, which one is 7a version here http://boeffla.df-kunde.de/bacon/boeffla-kernel-cms/cm11.0s_download/Test/Series 2.x (for XNPH38R)/ ?
[ONE Original Android Development] P1nGu1n_:
You were in the CM11s folder, this is the link to the CM11 folder where you can find 7a: http://boeffla.df-kunde.de/bacon/boeffla-kernel-cm/cm11.0_download/Test/
[ONE Original Android Development] ZaneZam:
7a is for cm11 nightlies since 01.11.14 only not for cm11s stock if u run 38R you probably run into the "previously flashed other kernel wlan issue" you can try to download the Cwm flashable wlan fix which Lord boeffla provides in the download area u posted (last download at the bottom) . But as the file says it's only for 38R stock roms so be careful. If that doesn't fix your problem afterwards u have to reflash the rom.
[ONE Original Android Development] BrunoNRG:
Thanks, I just did reflash the rom and wifi is back working
[ONE Original Android Development] magnamentis:
mentioning rom recommended

if you are on cm11s our previous trials to assist were nonsense and to the correct answer would be as mentioned by [MENTION=3279788]ZaneZam[/MENTION] but then i would strongly recommed to mention the rom you're using.

and for us (me) i will perhaps ask first haha.. just did not think about that and of course still not sure whether you're on cm11 or cm11s but at least it would explain the going in circles.

the reason why i and others assumed you're on cm11s is because there were indeed changes by cm in the nightlies recently which made 2.0 beta 7 incompatible with later nightlies. so if you're on cm11s. [MENTION=3279788]ZaneZam[/MENTION] gave you the hint in if you're on cm11 genuine, then you've just searched in the wrong download section. report back when you found a solution so that we can learn
[ONE Original Android Development] BrunoNRG:
The Cyanogenmod version I'm on is 11.0-XNPH38R, as I said first, the kernel I installed was boeffla-kernel-2.0-beta7-CMs-bacon.CWM.zip, downloaded from here: http://boeffla.df-kunde.de/bacon/boeffla-kernel-cms/cm11.0s_download/Test/Series 2.x (for XNPH38R)/ , probably I installed the wrong kernel....

I solved by flashing this rom Unofficial-cm-11.0-XNPH38R-bacon-signed.zip (found here http://xdaforums.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746) using a temporary twrp recovery I flashed using adbfastboot
[ONE Original Android Development] magnamentis:
ok sorry then

ok good to see that it's solved. as suspected later on, we were talking different things first because of the coincidence with the wifi commits and reverts on cm11 a few days ago. a simple misunderstanding due to premature assumptions about which OS you're on.
[ONE Original Android Development] BrunoNRG:
No problem :good:

So, what caused the wifi problem was me installing the wrong kernel for my Cyanogenmod version?
[ONE Original Android Development] magnamentis:
?

i don't know but to me it looks like you installed the correct version you'r on a recent cm11s build and installed the latest cm11s kernel, cannot see anything wrong there, but again i don't understand you. i understood you solved the issue so if it's working now you should know whether it was the correct version and what finally solved it. if it works now i'd say we let it be so :) as much sense it makes to agree on terms, i don't think that to do it here makes much sense. should anything be unclear still you can PM me.
[ONE Original Android Development] BrunoNRG:
It's working now with official 38R rom stock kernel, I guess I'll try to flash boeffla again, thanks for the help
[ONE Original Android Development] Shaddy-Z.:
What awesome results with a performance related configuration. I'm gonna try it I'm jelly! I always try to do battery oriented governors but I hate little lags when opening apps and going back to the home screen. Hopefully I get similar results on CM11s.
[ONE Original Android Development] RobbieL811:
How are people using this kernel tuning the sound control parameters? I added Boeffla Sound to my kernel, but I am getting FC in Boeffla Sound Control app when I try to access "Advanced Settings" Is this menu working for everyone else?
[ONE Original Android Development] andip71:
Probably you were on Franco kernel before?

Franco kernel hacks your wifi firmware, so it does not work with any other kernels anymore.

Only a fresh rom flash (as you did) can correct this. Or for some my wifi firmware restore zip file works too.

Boeffla-Config app in play store is not compatible to OPO Boeffla-Sound.

It will always FC as it is not maintained anymore, so cannot deal with OPO.

The app is not developed by me, so you would need to complain to the developer.

I do not recommend usage of this app anymore for a very long time. All users of my kernel us the Boeffla-Config V2 app instead, which lets configure Boeffla-Sound for all my kernels with all features.

But as Boeffla-Config only work with Boeffla-Kernels, this is not an option for you as well.

Andi
[ONE Original Android Development] andip71:
Hi,

to answer your questions:

1) No, I am not implementing a dialog that asks before you configure a change. This way it is much faster. You can create multiple profiles in profile maintenance screen, so you can have a normal one and as many as you want to play with. This is the philosophy of the whole app. Also pay attention to app documentation on the homepage to understand it more in depth.

2) It is correctly displayed. You probably compare applies and pies - kernel view of memory usage is not same as rom view due to having a VM in between. FAQ on homepage explains that too.

3) Why, is this text disturbing you at all? I did that on purpose to not end up with a completely blank screen when neither frequency nor voltage changes are implemented. Always bear in mind, my app works on many devices, Snapdragon as well as Exynos based, Mail as well as Adreno based. So I have to go for compromises sometimes.

Andi
[ONE Original Android Development] storm119:
Hello again...

1- Most probably i'm new to your app and have to get use with it....need more time for me to understand :)

2- alrite i just confused

3- ahh....understood (having thought that too...)

FYI...i read those documentations on the home page before post here...maybe i'm not read that hard...my apologies

...anyway thanks for your reply...really appreciates
[ONE Original Android Development] andip71:
Hi, no problem mate.

My app works a bit differently than others, but I am convinced you are faster when changing settings + the app is more powerful than many others.

1 - yes, take some time.

2 - the Android paradigma is: take as much memory as possible. So, the virtual machine (ART / Dalvik) tries to allocate all ram in order to maintain it for the rom and the apps. So my app (as it is a kernel configuration app) shows the kernel view = all ram almost used, which is good. And what you see in the rom is how much ram is still free in the VM. Also here it should not be too much, as the VM caches apps and data in order to reload it quicker if required again.

3 - no problem. I wish I could sometimes break some backward compatility to make things a bit easier. But so far I still cannot do it. Maybe in a year or so when I can remove the Exynos stuff the app was basing on initially (S3, Tab 10.1 etc.)

Cheers

Andi
[ONE Original Android Development] storm119:
Yes mate....i agreed with you. I love the simplicity (straight forward) of your app but yet a very powerful/configurable especially the tunable part and hotplug settings (profiles)....together with zzmoove governor/native hotplug (which i started to learnt) there looks awesome and interesting...anyway with the help of your app's, i hope to learns/discover the real potential of this kernel....thanks ;)
[ONE Original Android Development] andip71:
Yes, you will learn and love.

Also watch out for the dedicated configuration sharing thread. There people debate and exchange configurations that they come up with and provide it as importable files.

Andi
[ONE Original Android Development] storm119:
Haha yes sir...ive been there (profile thread) and already subscribe it + Unofficial boeffla - zanezam, ZZMoove Governer, KERNELS EXPLAINED, this thread + your home page :D
[ONE Original Android Development] andip71:
Good thing, mate.

And believe me... to unleash the maximum power of my kernel, you need my app. Many things are so much optimized, other apps can just not control it (also some things are by intention proprietary so I have better control over it).

Andi
[ONE Original Android Development] :
Anyone here had been using the undervolting ?

I have been using the undervolt light so far, didn't face a crash even while running benchmarks in antutu, just switched to undervolt medium.

Anyone has any personal experience to share in terms of undervolting CPU ?
[ONE Original Android Development] infatality:
I'm using -50mv since months ago with no crash or whatsoever.. I'm on PVS Bin 8.. Undervolting maybe a placebo effects for some.. But I have seen significant battery improvement with Undervolting and underclocking.. If you are looking at how low can you undervolt, it solely dependent on your PVS bin.. The lower your PVS bin, the higher your voltage. The higher PVS bin, the lower your voltages.. For your reference http://xdaforums.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
[ONE Original Android Development] storm119:
Since we discuss about undervolt (-UV)....hopefully our master [MENTION=947981]Lord Boeffla[/MENTION] wont see this...LoL :D

Anyway from my own experienced....i used to undervolting (+underclocking) my bacon since the day i use custom kernel without any ill/side effect...as result more cooler CPU + slightly more juice on battery (take this as a pinch of salt the result may vary). From my observation if one use other than zzmoove governor, one can extremely -UV to maximum for example on my bacon PSV 6 Bin 3 the stable is = -75 UV but with zzmoove governor the highest and stable is -50 UV (or with boeffla kernel's = medium). Bare in mind too much on undervolting may result of unstable and random reboot to your device....one need to find the best -UV for his/her device. My suggestions if you need to -UV...start from -25 UV and use for 1 hour if nothing happen to your device...start to increase to another level till you find the best -UV for your device.... ;)
[ONE Original Android Development] :
Since this is the first time I'm reading about this new concept, it seems that limiting the min and max frequency range delivers much scalability and better battery life ? I'm going through the post will take some time to grasp.

---------- Post added at 12:20 PM ---------- Previous post was at 12:14 PM ----------

So, say for example, when I'm sitting at min freq of 300ghz and max freq of 2457, and I undervolt 50mv, situation arises when i start an application that needs higher clock speed, and now CPU has to scale to say 1.5 or 1.7 ghz from 300, but there isn't enough voltage, and baam, it crashes, that explains how that happened on 75mv undervolt today when i just plugged in my headphone jack and started poweramp, but after booting, it didnt happen, cause i was using the phone at that time, and cpu freq must have already scaled much higher than 300 of course, so it wasn't that big leap. But what I'm guessing is, I use zzmoove-optimal, and it shouldn't scale up too much from sleep at 300mhz when i play music, [MENTION=3279788]ZaneZam[/MENTION], is the upscaling of freq application dependent or activity ?
[ONE Original Android Development] ZaneZam:
actually freq switching is mainly system load dependent but it also depents on all "scaling" settings as they of course influence that. (especially the "fast scaling" setting)

about undervolting: beside of that the "gambling" starts at the moment u guys touch any voltage slider it can be that zzmoove is much more sensitive

in combination with uv firstly as it scales very fast (on some devices people even have to OV to aviod crahes on higher freq because of that) and secondly as it does a lot of stuff in addition which other

governors don't do: depending on setting: sampling rate switching, cpu temp reading, touch recognising, etc.. + hotplugging if native hp is used which is always a "critical thing" even without uv)

so yes it might be that u can't use as much uv as with other governors but as often stated, here again: benefits of uv are anyway highly questionable!! my experience is: don't touch it = no problems and a stable system! yah yah i know but were is the fun then :D good thing is with boeffla u have the choice ;)
[ONE Original Android Development] andip71:
Guys,

my very personal opinion on undervolting is: Not worth risking stability (and therefore data and file system consistency) for it.

Benefits, as ZaneZam said already, are questionable.

But - you are of course free to try it. That said, I have not removed the option in my kernels so you have the freedom (I like freedom, sometimes at least :).

However: If you undervolt and face any issues - be sure I will not respond to questions, help requests or anything else.

You undervolt -> you run without my support. As simple as that, as stated in OP.

Andi
[ONE Original Android Development] andip71:
CM12.1 kernel maintenance update

Folks,

I am still hanging around in Florida, but as CM pushed a new commit after a loooooong time today and I had some time, please find a small maintenance update for my CM12.1 kernel.

CM12.1 -- Version

4.2-beta10

10.11.2015

Updated with latest official CM kernel commits as of 10.11.15

Ramdisk updated to official CM12.1 version of 10.11.15

Enjoy

Andi
[ONE Original Android Development] johnsin5393:
Any latest kernel support cos 12.1 3jl version? Thanks
[ONE Original Android Development] ZaneZam:
yes the latest kernel for COS12.1 is still working with 3JL ;)
[ONE Original Android Development] johnsin5393:
Which one? The v4.2beta10?
[ONE Original Android Development] andip71:
No. There is a reason why I provide a specialized COS kernel as well.

It is:

4.0-beta7

If you go on the kernel homepage, it is even the first one...

Andi
[ONE Original Android Development] Marek McFly:
I didn't read LordBoeffla's last (undervolting-)post. Sorry for my posting.
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] there's an kernel commits that supposed to fixed wlan buffer overflow. Possibly to get it on COS12.1?

https://github.com/CyanogenMod/andr...mmit/e728d16e1d068ced7727031e9a60596a08ba5359
[ONE Original Android Development] iccolatte:
-sorry deleted-
[ONE Original Android Development] storm119:
hmmm...have you try to go to the first page by OP or to op [MENTION=947981]Lord Boeffla[/MENTION] home page....?
[ONE Original Android Development] andip71:
I reviewed the patch already when I put it into the last cm12.1 kernel version.

My opinion is, this patch is not significant. I cannot see what it apparently tries to fix. You have the corresponding jira at hand, so we get some more information about it?

Andi
[ONE Original Android Development] infatality:
Roger that! Aye aye, Sir!:D
[ONE Original Android Development] xflowy:
is zen decision hotplug implemented? :)
[ONE Original Android Development] andip71:
No. I don't implement any custom hotplugging logic as per my objectives.

Andi
[ONE Original Android Development] xflowy:
but didnt you already added bricked, zzmoove and co?
[ONE Original Android Development] andip71:
No and yes.

Bricked = no, zzmoove = yes.

But zzmoove is not a hotplug implementation, it is primarily a governor including hotplugging optionally.

But in general, my close-to-stock objective makes me stick with mpdecision and that's it.

Andi
[ONE Original Android Development] molonad:
Hello Mistr, iam glad that you will support cm 13, i love your kernel, it is simple and everything works like it should.. But iam little Worried about marshmallow roms for oneplus now .. Most of them are caf based (that roms i Want to try becouse of optimizations and features) so i cant use overclock (i really csn see diference in app opening speed, and i Dont have problem with cpu throtling down, becouse I Dont play games with it) and it is for me disaster, i just hate this situation... It will end up that I will must to install caf rom again and be dissapointed with speed and battery again, and without your kernel.. I Dont know what to do.
[ONE Original Android Development] andip71:
Have no good advise for you.

I will not provide a CAF kernel but only CM. Reasons are mentioned many times for my decision.

So, you need to decide yourself what is important for you :)

Andi
[ONE Original Android Development] molonad:
Yes i know it, it Wasnt any request to you about makeing caf kernel, and i like that you wont do it.. I just didnt know where to complain and i know that you agree with me about caf...
[ONE Original Android Development] magnamentis:
hi andi,

just in case to keep you currrent if you're not already reading through the threads. since i got some background information i got aware that many if not most roms formerly based on cm intent to switch to AOSP base. would you stick to your cm only decisions even if most custom roms came aosp based as most of them were cm based under LP? not that i care, i always find my ways to make the devices look and behave the way i want but still, i'm not sure whether you are already aware of an eventual siginificant move away from cm to AOSP base and hence thought in our all interest to ask you that question, be it out of sheer curiosity as to what to expect just in case :) BTW a nice and safe trip home and i'm not sure about you monday announcement, after we all know you quite well haha.... :laugh:
[ONE Original Android Development] andip71:
I will likely stick with my decision, yes.

The thing is: I never use any other roms than CM itself, I am not a custom rom fan myself.

So making a kernel for it is a personal waste of resources for me.

But nothing is put in stone so far. We will see when the topic comes up in reality.

Thanks, I will be leaving here very soon, my flights are safe despite the Lufthansa strike, so I would be all set.

Cheers

Andi
[ONE Original Android Development] magnamentis:
thanks for replying, i myself was on cm through the entire kitkat period while roms under LP were quite nicely done :) i doubt that caused by several changes like SELinux policy, forced encryption and other stuff that will be so easy under MM and hence possibility is high that another CM year lies ahead for me too, while i'm not sure yet whether cm brings a rom for OP2, could be that they're stonewalling and then we have that laser focus and dual sim thingy which is not yet solved by a single rom maker till now. let's see, interesting transition times like every year. BTW the update to o2OS 2.1.2 was well taken till now, seems to solve quite a bunch of minor and significant issues. happy landing (later on) :cool:
[ONE Original Android Development] brisac:
Mind sharing future plans for cm13 kernel?:)
[ONE Original Android Development] magnamentis:
that's what he just did, more is not to say or what else do you have in mind he could answer other than that he's waiting for cm13 to be released and go from there but non-caf?

http://xdaforums.com/showpost.php?p=63807849&postcount=6828
[ONE Original Android Development] andip71:
Yeah, all said for the time being.

Already at Tampa airport now, so blackout in latest 3 hours for 12 hours.

Andi
[ONE Original Android Development] bloof:
Could anyone please upload a flashable zip of the stock COS12.1 3JL kernel?

Has to restore phone to old state and lost my kernel backups.

Thanks!
[ONE Original Android Development] vicky2131:
Boot.img from the factory image of 3JL.--> https://drive.google.com/file/d/0B1uwRLxZ7cuvSFRkYlZOZDIxSjA/view?usp=sharing

Hope you can make a flashable zip with the boot.img provided :)
[ONE Original Android Development] Mecca EL:
If you need anyone to alpha or beta test your planned CM13 kernel, let me know. I'm on an unofficial VM13 build, that's super stable.
[ONE Original Android Development] andip71:
Is now availabe in the stock kernel folder in the download area on my homepage.

Yes, when CM13 comes officially out, then I will work on a kernel. But I guess this is not before next year from what I see.

Andi
[ONE Original Android Development] andip71:
COS12.1 kernel update

Hi all,

the ones that already updated to latest COS (Cyanogen OS) firmware YOG4PAS3JL should flash the updated kernel to have best compatibility.

COS12.1 -- Version

4.0-beta8

16.11.2015

Note: It is required to update to COS12.1 version YOG4PAS3JL to use this kernel version !!

Update to be compatible with latest COS firmware YOG4PAS3JL

Enjoy

Andi
[ONE Original Android Development] Mecca EL:
Looking forward to it. You're the only kernel developer that offers Swipe2Wake. That's what led me here, then I discover how great of a build you've made. Thanks!! :highfive:
[ONE Original Android Development] bloof:
Thanks. Always the first place i look.
[ONE Original Android Development] bloof:
Beta 7 wasn't compatible? I had the impression it was working fine. Must be only minor changes.

Thanks for the update!
[ONE Original Android Development] andip71:
It was probably 99,9% compatible.

I just realized last time on the OPO of my wife, wireless was dropping from time to time when rom and kernel ramdisks are not matching exactly.

Andi
[ONE Original Android Development] bloof:
Ah! Wifi crap. I thought it was a problem with the new ROM!

Did she also have problem with updating google apps and phone just reboots after installing and actually installs several versions of each bloody google app (google plus, hangouts, etc)?

I know, that's a ROM issue, been happening since 12.1, just driving me nuts. No worries, just had to vent on that one.
[ONE Original Android Development] andip71:
Nope. She had only the wifi drops fortunately.

Andi
[ONE Original Android Development] twowheeler:
Thanks for explaining. Was already wondering what the difference was, or what was changed. This explains it I guess. Great kernel as always. Running like a dream!
[ONE Original Android Development] atulclassic:
Why the min freq jumping again to 2.5Ghz..using beta 8 with build 3JL
[ONE Original Android Development] andip71:
Synapse?

My kernel cannot be controlled by Synapse. Not sure if you are in the right thread.

Andi
[ONE Original Android Development] Setting.Out:
I may have missed the question, if posed, but will you update KitKat for security patches?
[ONE Original Android Development] infatality:
It's an rom issue not related to kernel.
[ONE Original Android Development] andip71:
No. All the security patches are not affecting kernel code.

So, no need.

Andi
[ONE Original Android Development] andip71:
CM12.1 kernel update

Hi all,

quick maintenance update for the CM12.1 kernel, after a new nightly came out again today after many days.

CM12.1 -- Version

4.2-beta11

18.11.2015

Updated with latest official CM kernel commits as of 16.11.15

Ramdisk updated to official CM12.1 version of 18.11.15

Enjoy

Andi
[ONE Original Android Development] Shadow Samurai:
I've got a mic speaker volume issue I think was caused by this kernel's latest update. Cmos12 build. I'll let you know if the issue goes away when I revert kernel

I can hear them but I am cutting out when I talk back

Sent from the one and only Oneplus One