yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
Following the close-to-stock ideology, I leave that up to the mpdecision/thermald processes that come with a rom.

So, it is cared about the same way as with a stock kernel.

If this does not yet work 100%, then it is due to the alpha status.

On the other hand, something is not quite right if you encounter that more often. I never had anything like that since I use CM12 on my opo.

yes, kexec patch is contained on all my kernels for the OPO.
[ONE Original Android Development] acidburn94:
Ahh ok thanks, will you support oneplus one as well or not? It would be a great thing:) anyway your kernel rocks, best one ever tried!!!
[ONE Original Android Development] andip71:
Thanks for the nice words.

I need to check first whether this makes sense at all on an Qualcomm device, if yes, I can try to enable it.

Give me a few days to check it pls.

Thanks

Andi
[ONE Original Android Development] andip71:
Have you configured anything special? Overclocking, undervolting etc?

And to send me the last kmesg is simple: Just create a so called "debug info file" directly in Boeffla-Config app (last point of Action Menu button)... this will include lots of debugging information, also last_kmesg of course :)

Andi
[ONE Original Android Development] pantmunu:
Nothing special. Intelliactive with standard and clocked at 2.5 GHz. That's all. Weird . but I guess its the facebook app itself. Standby time with the zzmoove governor and optimal setting is just awesome . great work sir . and yes .. Will do that in a bit.
[ONE Original Android Development] ZaneZam:
Consider to overvolt to +25 or +50mv at all oc freq, I never had to do this when I oc on the S3 but this device obviously is more sensitive ;)
[ONE Original Android Development] andip71:
Yes, seems I have a very tolerant device.

But I consider increasing the OC frequency voltages by 25 mV as default for the next beta. Maybe...

Andi
[ONE Original Android Development] pantmunu:
Will do and yes .. My device can't handle undervolting so ... No undervolting for me and I actually haven't found uving that healthy though .. Will see if overvolting helps. Thanks again.
[ONE Original Android Development] NickosD:
Yep, I also have problem with I.. I can even pass the antutu test because of cpu.
[ONE Original Android Development] andip71:
Important note to everyone:

In the current beta version, the Kexec hardboot patch is

NOT

working in beta1.

It will be fixed in beta2, a user already tested it successfully some minutes ago.

So, things are moving on :)

Andi
[ONE Original Android Development] Herr Olsen:
I have flickering horizontal bars across the screen from time to time. Happened in lockscreen, couple of apps and camera.

They usually disappear after screen off.
[ONE Original Android Development] NickosD:
I'm stuck in a boot loop...... Boeffla app doesn't find an error and it applies the settings again and I can make it in time to change them. Can you make a file for these situations?
[ONE Original Android Development] marcowind80:
Into boeffla dir there is a reset file to apply by recovery
[ONE Original Android Development] andip71:
Never had that ever seen on my device.

Maybe the new GPU drivers in latest version of rom/kernel are not yet 100% mature.

In boeffla-kernel-data folder, there is a reset zip. If you flash that zip in recovery, everything will be reset to default, so you can boot again.

BTW... this is all covered in the documentation on the kernel homepage. Please read at least the FAQ !!!

Thanks! Obviously you did the reading :) :good:
[ONE Original Android Development] NickosD:
I find this file inside boeffla app?
[ONE Original Android Development] andip71:
No, see what I have written above.

Or do some reading of basics on kernel homepage. Please.

Andi
[ONE Original Android Development] NickosD:
I read it and still can't find it.
[ONE Original Android Development] mcrane1981:
Always used Boeffla kernel back in the GS3 days. Glad you're here. Thanks man.
[ONE Original Android Development] andip71:
How should we help you further...

Enter recovery and flash the file boeffla-config-reset-v3.zip which is located in boeffla-kernel-data folder.

That's all.

Andi
[ONE Original Android Development] NickosD:
Ohh I got it now.
[ONE Original Android Development] sui81:
I'm proud to use a Beta Build from Lord for my One+, witch runs Multirom with CM11 based Temasek and CrDroid Rom.

Works like a charme and much smoother as AK Kernel, with witch i must use higher Clock Rate to get fluid and no need to use any Apps (Synapse/Trickster) for Setting up, things like Min/Max Clock, I/O Scheduler or Gouvernor, i can now use the Rom internal Power Manager.

Please donate for this Dev, for buying a second Device to official support CM11/AOSP Kernel.
[ONE Original Android Development] andip71:
Phew... Good [emoji2] [emoji106]
[ONE Original Android Development] Steelpapi:
I had the screen flickering thing. It happened while I was watching a video on MX player and had a call interrumpting the video. After I hanged up, the flickering started. Had to reboot and then the problem disappeared.

I'm hoping you will enable the Equalizers soon! This is my main reason for using this Kernel! Many thanks!
[ONE Original Android Development] nicesoni_ash:
Sweet. Thanks mate.

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] fjsferreira:
[MENTION=947981]Lord Boeffla[/MENTION], does your kernel include this?

http://review.cyanogenmod.org/#/c/77918/
[ONE Original Android Development] P1nGu1n_:
That commit was committed 18 November, so the latest beta's don't include them, since they're released 17 November. Latest CM12 alfa (alfa3) should, it contains every CM kernel commit as of 21 November.
[ONE Original Android Development] fjsferreira:
But, as this wasn't, as far as i can see, merged, will the alpha 3 cm12 kernel still include it?
[ONE Original Android Development] acidburn94:
As much days as you want, your kernel it's fantastic right now, with that implementation would be amazing:) thanks Lord!!
[ONE Original Android Development] P1nGu1n_:
I'm sorry, overlooked that one. Just looked at his Github and alpha3 is still using Touchscreen Firmware version 0x13077405, not the new 0x13077406 from the commit you referred to.

https://github.com/andip71/boeffla-...input/touchscreen/synaptics_firmware_wintek.h
[ONE Original Android Development] orangerot.:
Hey,

I have a little suggestion regarding your governor profiles (please correct me if I misunderstood something).

For example in the interactive battery profile the highspeedfreq is set to 833200, the go_highspeed is 95, meaning if the load is 95% the cpu will go immediately to 833200?

If that's correct the touchboost frequency of 1497 doesn't make much sense as the frequency is going to 1497 and therefore the highspeedfreq is only used when the device is not in use? (when do you use the device but don't touch the screen? Except for watching videos or so)

For me that doesn't make much sense (so I set touchboost to 833 to match the highspeedfreq and I don't notice a loss in performance).

Please correct me if I'm wrong :D

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] luigirenna:
Hi,

really a great kernel.

I installed version 3.0 Alpha 3 on cm-12-20141124-UNOFFICIAL-temasek-bacon-Preview-3.

I noticed two things.

1) in app "Boeffla Config ver. 2.1.54" the sliders for audio seems to have no effect on a BT headset connection.

2) if i are connected with WiFi and re-enable the screen for a few seconds I am active in WiFi and 3 g.

WiFi setup I enabled "Keep Wi-Fi on during sleep"--> Always.

I hope that I discussed well.

my English is like Joda.

Anyway great Kernel.
[ONE Original Android Development] andip71:
Not, it is not in official merge state, I have not included that so far.

1) Normal, Boeffla-Sound works on the DAC audio chip, this does not include Bluetooth (and cannot).

2) Yes, this is a glitch in all CM12 roms around so far.

Whats you suggestion? Any proposal?

Thanks

Andi
[ONE Original Android Development] orangerot.:
My suggestion would be to apply the same touchboost value as the highspeedfreq is, when a profile is applied. As already said for me it works fine with 833 as touchboost and highspeedfreq, letting the cpu stay on lower frequencies while doing simple stuff like texting and jumping up to higher frequencies when the power is needed. For me it's a bit overpowered to raise the clock to 1,4ghz just because I write a message on whatsapp. So in my opinion it's more useful to set them to the same level, or lower the touchboost to eg 833 and the highspeedfreq to 1,4 ghz(just an example). In this case we'd boost the clock to a frequency which is fine for simple stuff like texting and the frequency would be raised quickly if we're doing stuff which needs more Power. This should lead to a more efficient power/performance relation?

What do you think about that? Or am I completely on a wrong way with that suggestion?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] luigirenna:
Dank
[ONE Original Android Development] Dima_2005:
Isn't binning also an issue? I thought that some bins actually perform much better on lower frequencies, regarding the efficiency. On the other hand, some bins really need higher freq for relatively good performance.
[ONE Original Android Development] orangerot.:
I don't know about that, but it'd still be better the other way? That go_highspeed is there to boost the device if the load is high. If the touchboost is higher than that it would almost never be used.
[ONE Original Android Development] andip71:
Well, two things here:

Touchboost is standard functionality which is built into the stock kernel even.

In stock kernel it works with a hard 1497 Mhz frequency, all I did was to make that configurable.

So, touchboost is available regardless of chosen governor.

What you are referring to is governor specific tunables. This go_highspeed you are talking about is only there in interactive. But not on other governors, like ondemand, zzmoove etc.

So this is only for interactive users, users of other governors would be missed out if we did not have touchboost as well.

I do not see any issues really, as you can tune your interactive governor as you like + adjust the touchboost frequency also as you like. So both things are independent of each others - and they should be that way even.

There is no conflict at all etc.

Andi
[ONE Original Android Development] andip71:
New app will support theming

Hi all,

especially in the light of having Android 5 coming on our device soon, I was tired to see the quite "old" and dark holo design in Boeffla-Config all the time.

While I still like it on Android 4.3 or 4.4 roms, it breaks user experience on Android 5 for me.

Hence, I made the app now supporting designs. For the start you can choose between holo (this is the current standard), holo light, material and material light themes (the latter two only available if the app is used on Android 5).

And I really LOVE to use material light design on my CM12 based OPO :)

Just as a teaser for you, as I am still testing it upside down...

Andi
[ONE Original Android Development] orangerot.:
Yes I know it's not available on other governors. Also my intention was not to change that behavior in general for the standard interactive profile, but for the battery saving profile, so users who don't know how to tune the governor/touchboost can profit from lower clocks and (maybe) improved battery life.

But if you think it's not the right way to preconfigure it this way, I'll keep doing it by myself ^^
[ONE Original Android Development] andip71:
Ok, I might consider that for the future.

Currently, the presets cannot influence the touchboost frequencies at all. That is a limitation of the current config app. But of course everything can be changed :)

Thanks for the suggestion, now I finally got your thoughts.

Andi
[ONE Original Android Development] nicesoni_ash:
Hi Andi

Sorry to disturb you again but I have one more question.

I learned that to run lollipop based rom as secondary roms using multirom, kexec patch has to be updated so just want to know whether the included kexec patch in this kernel is updated with latest changes to do that. Thanks

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] andip71:
Probably not then. I never use multiboot myself, so I never tested this (and will not as long as I need TWRP for that).

But where did you learn that? Maybe I can do some digging for you.

Andi
[ONE Original Android Development] nicesoni_ash:
As per this post..

http://xdaforums.com/showthread.php?p=57028425

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] andip71:
Ok, thanks for the heads-up. It is not in alpha3, but I just merged it. So it will be in alpha4.

Time to compile a new alpha eh? But no more changes by the CM team I can merge in. So I am a bit reluctant to just do a new alpha for this little change.

Let's see if they have additional patches in a few hours.

Andi
[ONE Original Android Development] Han-Droid:
Sorry for going off topic...but..can anyone point me to a solution for call recording with cm11s ?

I read that it's easy with CM11. I just don't wanna leave cm11S only for being able to do call recordings.

I mean there are apps but they kinda offer a second-best solution only....

Tia for any thoughts on that!
[ONE Original Android Development] Roman91:
https://developer.android.com/design/patterns/navigation-drawer.html

what about this? :p :):)
[ONE Original Android Development] molonad:
i saw some posts where people share their display settings in their official stock settings - i red that month ago , but that settings was deleted by cm.. dont know why.. People were really satisfied with this options and they said that colours looks better with some adjustments. So i really want to try that.

i red that here http://xdaforums.com/oneplus-one/themes-apps/screen-color-setting-t2823879

---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------

i saw some posts where people share their display settings in their official stock settings - i red that month ago , but that settings was deleted by cm.. dont know why.. People were really satisfied with this options and they said that colours looks better with some adjustments. So i really want to try that.

i red that here http://xdaforums.com/oneplus-one/themes-apps/screen-color-setting-t2823879
[ONE Original Android Development] acidburn94:
Lord Boeffla what do you think would be better: cm11s with your amazing kernel 2.0 beta 10 or cm12 (if yes which one? K900one?) with your alpha 3 kernel? :) especially for battery life!

Thanks my lord:)
[ONE Original Android Development] f100cleveland:
I'm not Lord, but I would recommend cm12 and I don't think it matters who its from, as long as its the latest nightlie. Get that setup, then once it's settled, you can flash alpha 4 ;)
[ONE Original Android Development] andip71:
Hi there,

meanwhile I had some time to look into that.

The idle mode setting is specific ONLY to Exynos CPUs, this is not available on our Qualcomm SoC here (and most likely also not making any sense there).

So, this cannot be enabled ever.

Andi
[ONE Original Android Development] andip71:
I have to be honest - cm11s is what I would say.

CM12 is in very early days, although it improves a lot on daily basis.

However, battery life is by far not as good on CM12 for me than on CM11s.

So if you use your phone as a daily driver, I would recommend to stick to CM11s and use beta10 (ok, not long anymore, then beta11, hehe).

But this is only my personal opinion.

Andi
[ONE Original Android Development] acidburn94:
Really thanks, I will use cm11s and for now the beta 10 the 11 when it will be ready hehe:) thank you for your suggestions :)
[ONE Original Android Development] andip71:
Guys,

quick heads up for a bit later...

2.0-beta11 is compiled for cm11s and cm11 -> testing ongoing

3.0-alpha4 is compiled for cm12 -> testing ongoing

Will release in a few hours for all of you.

Cheers

Andi
[ONE Original Android Development] DerRomtester:
Thank you very much :)

Dont forget to push the source code. I am curious.
[ONE Original Android Development] andip71:
When it is make public, then the code is pushed. Of course :)

But you will be a bit disappointed this time, only a few changes done which are very much Boeffla-centric.

Cheers

Andi
[ONE Original Android Development] nicesoni_ash:
I have a question regarding cm12 kernel. If I am flashing cm12 as secondary but have cm11 as primary using multirom, what Kernel should I use?

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] andip71:
No clue. I am not using multiboot myself, never did.

But I am sure somebody knows it...

Andi
[ONE Original Android Development] nicesoni_ash:
Will try both versions.. :D

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] andip71:
Finally - new betas/alphas for cm11s, cm11 and cm12

Hi all,

kernel updates of all my kernels now - cm11s, cm11 and cm12.

Change logs are as follows:

CM11s - Version 2.0-beta11

26.11.2014

New touchscreen firmware (18.11.14)

fstrim in Boeffla-Config app using internal fstrim command now

frandom removed completely and disabled in Boeffla-Config as it turned out it did more harm than good (e.g. breaking wifi on cm12 etc.)

Option in Boeffla-Config to install full busybox deactivated (OPO roms come with fully stuffed busyboxes already, so this was useless)

Internal su updated to version 2.30 beta

Internal Boeffla-specific hardening and bug fixes in startup- and controller scripts

CM11 - Version 2.0-beta11

26.11.2014

New touchscreen firmware (18.11.14)

fstrim in Boeffla-Config app using internal fstrim command now

frandom removed completely and disabled in Boeffla-Config as it turned out it did more harm than good (e.g. breaking wifi on cm12 etc.)

Option in Boeffla-Config to install full busybox deactivated (OPO roms come with fully stuffed busyboxes already, so this was useless)

Internal su updated to version 2.30 beta

Internal Boeffla-specific hardening and bug fixes in startup- and controller scripts

Ramdisk updated to version of nightly 26.11.2014

CM12 - Version 3.0-alpha4

26.11.2014

New touchscreen firmware (18.11.14)

Updated Kexec hardboot for Android 5

fstrim in Boeffla-Config app fixed (using internal fstrim command now)

frandom removed completely and disabled in Boeffla-Config as it turned out it did more harm than good (e.g. breaking wifi on cm12 etc.)

Option in Boeffla-Config to install full busybox deactivated (OPO roms come with fully stuffed busyboxes already, so this was useless)

Internal su updated to version 2.30 beta

Ramdisk updated to inofficial CM12 build of 26.11.14 by daleski75

Enjoy

Andi
[ONE Original Android Development] nicesoni_ash:
Thanks for the update but does cm11 kernel has the kexec patch updated too coz if I flash this as my primary rom Kernel, it will only allow me to flash lollipop as secondary rom if it has the updated patch.

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] andip71:
Cm11 kernel does not have the updated patch, no.

Only the cm12 one.

As I never use multiboot myself, I was not sure if it is required.

Andi
[ONE Original Android Development] nicesoni_ash:
It is required so may I request you to kindly update that too?

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] andip71:
You may always ask, of course :)

I will first compile a test version of the cm11 kernel for you and let you know.

After you confirmed this is all ok, I will update the kernels for the public etc.

Thanks

Andi
[ONE Original Android Development] magnamentis:
works well, thanks

hi andi, just out of curiosity i attached a screenshot with the overview page to ask whether it's intended that on the left of the app version there is no more kernel-version check. it's gone for me since i flashed beta10 pre-release if you remember which one, the one which we used to check on-boot settings ;) since the version is shown right below in detail it would be totally ok to stay like this, only perhaps the red color when a new version was available was convenient but the main reason i'm asking is that i wanna make sure to have a perfectly working config before cm11 developement will be abandoned entirely upen cm12 release :)
[ONE Original Android Development] andip71:
magnamentis: No, it has nothing to do with the kernel etc.

You simply lost your donation status. This came with last app update, which now requires you to use your personal donation code.

Probably you have not yet entered it into Boeffla-Config settings. Thats all.

If you donated via a donation app from play store, go into it and follow the instructions to get your code sent :)

Once you put your code in, all the functionality is back as you know it.

Cheers

Andi
[ONE Original Android Development] andip71:
You have a pm with a test version...

Andi
[ONE Original Android Development] magnamentis:
no did not use an app but found the code in my email, we did that manually, thanks for the quick reply will enter the code now :)
[ONE Original Android Development] _Beni_:
New version seems stable as always ;)

Anybody can tell me why 1267Mhz and ZZMoove, bfq + 256KB and Hotplug optimized is smooth and my old S3 was not even with 1,6Ghz so smooth?
[ONE Original Android Development] ZaneZam:
maybe the difference comes also from the fact that the opo has "infinite" ram :)

i was never able to get a complete smooth system with the S3 (in combination

with pure stock roms) because of a for me "sticky" out of ram/lmk problem in recent 4.3 roms

zram/lmk adjustment helped but only for some time. the S3 is really limited with its 1 GB
[ONE Original Android Development] Hana88:
boeffla can you do ANYTHING for the gaming lag?

Try any 2d game (like ski safari) and some 3d games...

If you see, there is a lag on the gaming, if you change the governor on conservative and I/O scheduler to NOOP, you will see more smooth game...

https://jira.cyanogenmod.org/browse/BACON-1719
[ONE Original Android Development] andip71:
If you would read the op carefully, you would know I do not care about gaming at all.

So I do not know if something lags or not.

And I will also not try any game ever. Sorry, too old for that.

So please excuse my ignorance here.

Maybe others can help you with good settings proposals...

Andi
[ONE Original Android Development] SaschaKH:
Just found a somewhat odd behaviour. I had the CM11s beta 10 kernel and used load & flash from the action menu. As it updated to beta 11, it wrote loading CM/Omni kernel.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] DjDiabolik:
Usually for upgrade this kernel i made this pass:

1- Reset the Config App and my 1+1 has been restart

2- At restart i wait some seconds.. and restart again on Recovery

3- From TWRP flash newest version...

4- Before to restart wipe cache and dalvik cache and restart

5- Wait some seconds and from config app i made all my preferred changes.

It's correct this procedure?

But my question it's.... it's all necessary ? i can upgrage following a different ways?

What you can suggest to me?