yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] tracerit:
Yeah i'm referring to the nav bar on the bottom. A lot of our interaction with the phone is with the bottom portion, I just figured it'd be more convenient. I tried the swipe capacitive buttons to sleep but coudln't stand the hardware buttons. Swipe screen to sleep was cool but got in the way of keyboard swiping. Double tap notification/status bar was not convenient because it's high up and my phone mount in the car holds from the bottom half of the phone so it would rock the phone too much. Those are just my experiences.

My ROM currently does not allow the on screen nav bar and capacitive buttons to be used at the same time (Euphoria ROM).

Thanks for the reply.
[ONE Original Android Development] Formhault:
Damn it. :(

Okay. Uninstalled MultiROM... performed a clean install of the latest CM11S unoficial build + Boeffla 2.5. Gonna sit here until 5.1.1 gets out and WORKS AS IT SHOULD (Wi-Fi, ffs).
[ONE Original Android Development] RcrdBrt:
Yeah, that's a really nice PRO feature to add. I hope to see that thing sorted soon.

If you don't mind I beg you to update me about this when you're testing it
[ONE Original Android Development] acidburn94:
Hi lord boeffla I would like to know if there will be the possibility to have your kernel on oxygen o's:) hope to have it soon:)
[ONE Original Android Development] andip71:
Before OnePlus do not release the kernel code, no custom kernel can be created.

Andi
[ONE Original Android Development] fmc000:
Well, as they MUST release it because of the license, anyone interested should push OnePlus in this direction.
[ONE Original Android Development] andip71:
Thanks.

Just for expectation management on sound: The OPO has NO Wolfson Micro Audio hub built in, so it means Boeffla-Sound will be limited to the bare minimum.

If someone can get me some technical register and specifications documentation on the wdc audio hub used here, more might be possible. But I think this is not freely available anywhere.

Andi
[ONE Original Android Development] andip71:
It is not on the feature list, and hence it is not supported.

And sorry to say: It will never be supported. f2fs is specifically mention as an all-time no-go in the OP.

Andi
[ONE Original Android Development] andip71:
That is my point as well.

Why should I use CM11 when CM11s is tailored to the OPO?

But as I said... it is more philosophic and a matter of personal taste.

So everone can and needs to decide.

I made my decision :)

(probably it would work with an exchanged cm11 ramdisk, yes. I just have no device to try)

Andi
[ONE Original Android Development] dafonehacker:
Nice to see you here Lord Boeffla! I remember installing your kernel on a friend's Galaxy s3 and he liked it a lot!

A little question: what does the beta mark mean? Does it mean it isn't fully tested or could be unstable, or does it just mean it isn't feature complete yet?
[ONE Original Android Development] artyfarty:
yahoooooooooo!!! :D :highfive: :good:
[ONE Original Android Development] hassan_1000:
Coming from the S3 with boeffla kernel i can't wait to flash on my opo!
[ONE Original Android Development] ZaneZam:
If I may state my lord: It's fully tested as always and leaves the factory ONLY in a stable state ;) but u never know only time and multiple installations can tell us if it's stable enough at "the end" but this is a complete new project so yes the feature aspect applies here too.

That's why i (and I assume all of us) like boeffla stuff so much : Quality first!
[ONE Original Android Development] andip71:
Basically what ZaneZam wrote is fully correct.

But yes... this is the very first beta, the kernel is maybe 2 weeks old until a first running build was created.

So it is like a 2 week old baby, it needs to grow, and yes... it can still be full of bugs. And most likely is.

But this is where we need you guys to help us finding them :)

Of course I would prefer if you do not find any, but that is not realistic.

So... let's go on that journey together!

Thanks

Andi
[ONE Original Android Development] NeGriTa79:
Good evening, what do you recommend settings?
[ONE Original Android Development] NOSTALGIA:
the most amazing dev. kudos..
[ONE Original Android Development] hughfollett:
Latest 38R update is finally on par with nightlies features, and 11S is more stable IMHO. I second your decision ?
[ONE Original Android Development] osmosizzz:
Oh snap!! The original developer of boeffla kernel. I used the galaxy note 2 earlier this year and someone ported somone features of your kernel to work with the apps and I loved it! Made the listening experience so much better. Just flashed cm11. Thinking of going to cm11s to try this kernel. This has a Yamaha DAC. Will you be supporting some features such as DAC clock change as well as decoding options?

Sent from my OnePlusOne
[ONE Original Android Development] Herr Olsen:
I literally prayed for this moment since I exchanged my S3 for an OPO.

Welcome to the dark side.

We have bacon!
[ONE Original Android Development] Han-Droid:
Alter! Wie geil ist das denn? Jetzt wird alles gut! !

Welcome Andi, you rocked the S3 and you will rock the opo! :) :)
[ONE Original Android Development] andip71:
Umm, personally I use the Boeffla-Kernel default settings which come directly after installation with only the following changes:

Governor = intelliactive

Scheduler = zen

No CPU overclocking or undervolting

Touchboost freq = reduced to 1294

USB charge rate = 900 (my PC can take it)

zRam on, 4 devices, 100 MB total size (but this is only for my internal testing about when it gets used)

Both loggers switched to off.

Well, I would not concur to that. There are many brilliant devs around here on XDA.

Absolutely, my opinion as well.

I would love so. Time will tell what is the art of the possible.

To start I would need some technical documentation about the WCD9320 audio hub. Then I could check what can be done, and what not.

But it seems you know some kernels which have these features implemented. If it is for this or a very similar audio hub, I could potentially port some of the features to Boeffla-Sound.

Although I do not see myself as a man from the dark... I liked the sentence.

Especially the following "we have bacon", which made me hungry again. Hehe.

Let's see. I will do my best to have one of the leading kernels as well in this area. But in the end it is about the users to like it or not.

I will still follow my proven approach, which is not very democratic, I know. But I will only put into the kernel what I need and what I like. In the past in the Samsung Galaxy area, this approach was quite successful :)

Cheers and good night

Andi
[ONE Original Android Development] NeGriTa79:
Not use the new zzmoove ???
[ONE Original Android Development] andip71:
I used it for many days during testing phase with ZaneZam.

And he is still fine tuning it.

But for me it is also important to look at the other governors, if they behave stable etc.

Und as I have been asked what I use currently... it is intelliactive in that minute :)

I am not yet having a stable configuration, too early, still checking, testing and experimenting. On top I know, Zane is having zzmoove in heavy testing anyways, no need to double the efforts here :)

Andi
[ONE Original Android Development] NeGriTa79:
Thanks for the replies ... I will try very happy your kernel !!!
[ONE Original Android Development] MMWolverine:
Finally out, it's a shame wasn't able to test alpha.
[ONE Original Android Development] Arise:
Sorry, don't understand exactly how touch boost should work.

So, if I touch the screen, it overclocks?

Anyway, set the max frequency at 2.8GHz and only the first and the fourth core are running at that speed.

It seems that the second and third core are stuck at 2.45Ghz.

If I start tapping on the screen like crazy, I see that both second and third core are jumping shortly at 2.8Ghz, but they quickly go back. So this is the reason why I'm tapping on the screen, to keep them boosted.

Also noticed that setting the CPU governor from your tool to performance won't set it on performance. I need to get in the phone settings and check the performance governor to actually keep it at 2.8GHz.

Any opinion on this? :)
[ONE Original Android Development] andip71:
Hm, cannot comment. Never had any app crash since I have my OPO.

I doubt pretty much it is related to the kernel.

But if you want to go 100% sure, reset your kernel configuration in Boeffla-Config, restart your phone, and see again.

If I come across crashing apps somehow, I will have a close look.

Andi
[ONE Original Android Development] Hexxer:
I did not change anything related to the kernel. Everything is default. Will try it next time.

Regards
[ONE Original Android Development] MobileThrowAwayAcc:
Seems with beta 3 I lose the ability to turn on my wifi. Otherwise the performance appears to be pretty great. Haven't used it long enough to comment on battery life.
[ONE Original Android Development] andip71:
Have you installed a different custom kernel before?

Some overwrite some wlan libs of the rom. Which renders it incompatible with other kernels.

You would need to flash your rom over again to have standard libs installed again.

Wifi works fine with a proper installation and without messing with rom libs.

Andi
[ONE Original Android Development] MobileThrowAwayAcc:
Great point, I did flash the stock kernel back before flashing yours- I'll give this a try and report back. Thanks!

Edit- I'm feeling a bit like a fool, but is there a link somewhere to the latest CM11S r38 as a flashable zip?
[ONE Original Android Development] andip71:
Sorry, but if libs are messed up, flashing stock kernel will not help.

You need to flash the rom over.

Maybe I should provide a cleaner zip to flash in recovery to correct this again when it was messed up before... Might be easier.

Can quickly do that tomorrow for convenience if all... ☺

Andi
[ONE Original Android Development] MobileThrowAwayAcc:
Understood, a cleaner.zip would be fantastic, much more convenient certainly than flashing the stock rom again. But in the mean time, am I crazy for not being able to find CM11s r38 as a flashable zip?
[ONE Original Android Development] andip71:
Yes, here you go...

http://xdaforums.com/showthread.php?t=2898098

Because I cannot promise a cleaner zip for tomorrow already... But you can just flash that over.

I used it as well...

Andi
[ONE Original Android Development] MobileThrowAwayAcc:
Fantastic, thanks! I had seen that previously but I guess I'm not used to equating stock and cyanogen (I was thinking it was AOSP for some reason)- sorry for not finding it myself.
[ONE Original Android Development] osmosizzz:
can I request double tap to wake in the kernel? apparently its not on, kernel wise. or am I missing something? and btw, flashed the kernel again and my sound issues from last time are gone :)
[ONE Original Android Development] MobileThrowAwayAcc:
But this is an option at the ROM level.

Settings-display-double tap to wake, yeah?
[ONE Original Android Development] osmosizzz:
It can be turned off kernel side too. I flash AK. Double tap to wake works. I flash boeffla and double tap to wake doesn't work.

Edit. Well I feel stupid. When I flash boeffla kernel I have to go to the settings to turn it on. Never mind people. Carry on. My ignorance won today lol

Sent from my OnePlusOne
[ONE Original Android Development] andip71:
Hehe, was just about to ask you to check it.

Double touch to wake is unchanged in my kernel. So it could only be the rom has deactivated it for any reason.

Glad you sorted it :)

I use it all the time (in fact this is one of the functions I love the OPO for). So if this would not work anymore, I would be the first one to notice in my pre-tests :)

Andi
[ONE Original Android Development] andip71:
Hi,

do not know if you flashed already over. But if not... here we go for the flashable zip (in recovery) which will bring the wifi firmware back to 38R stock.

So everyone who flashed another custom kernel before, that modified the wifi firmware that comes with the rom, can flash this zip to be back on stock.

This is required to make wifi work again with my kernel, many other custom kernels that do not replace the firmware, and even stock kernel.

You can find this zip also along with the kernels in the download folder on the kernel homepage.

So, in 10 minutes I will release beta4 :)

Andi
[ONE Original Android Development] andip71:
Beta4

Hi all,

please note, there is a 2.0-beta4 version now for you with the following change log:

Version 2.0-beta4

22.10.2014

Rebased to latest updates in CM shipping branch as of 21.10.14

First set of presets available in Boeffla-Config

Flash in recovery or via load&flash functionality in Boeffla-Config.

I will soon also release a similar beta4 for genuine CM11, same functionatlities as the cm11s kernel for 38R here.

Cheers

Andi
[ONE Original Android Development] poczynek:
Can't wait for cm 11 one thanks
[ONE Original Android Development] andip71:
Hi all,

Version 2.0-beta4 is now also available for genuine CM11.

Note: It does work only on the latest nightlies, not the old snapshot M11 anymore!!!

All features are exactly the same as for the cm11s kernel version.

Please download from the kernel homepage www.boeffla-kernel.de.

Enjoy

Andi
[ONE Original Android Development] poczynek:
Lord any difference to your settings since you posted them a while back?
[ONE Original Android Development] andip71:
Well, yes... I am playing around a bit.

Currently I am on interactive governor, with deadline scheduler and readahead buffer set to 1024.

Still no oc or uv.

Rest is as it was.

Andi
[ONE Original Android Development] andip71:
New Boeffla-Config V2 app is out, version 2.1.50.

This time you can automatically download and install it, hope it is working fine for you.

Version 2.1.50

22.10.2014

Improve CPU scaling on Qualcomm devices

Text improvements for WIFI scan interval

Updated Hungarian translations (credits to szunyi77)

Cheers

Andi
[ONE Original Android Development] :
Just did same thing, except on 2.6beta
[ONE Original Android Development] Han-Droid:
Let's say I had a sudden reboot and I had all loggers turned on....at what do I have to look in the logs to get an idea what triggered the reboot?
[ONE Original Android Development] andip71:
Last_kmsg in /proc folder.

Simplest is to let Boeffla-Config create a debug info file, everything including last_kmsg is included there.

Andi
[ONE Original Android Development] andip71:
Look out there for "kernel panic" or everything that looks like lot's of hex codes (register dumps).

Andi
[ONE Original Android Development] Han-Droid:
O.k.

Is

“ Kernel panic - not syncing: L1 nonrecoverable cache error detected“

a serious message?
[ONE Original Android Development] andip71:
No, this is just pointing to an inconsistency in the memory of the cache.

It could not be corrected, hence the panic.

If you do not undervolt (with undervolting this is a usual pattern), this should be a sporadic one-off error only.

If you do not undervolt and have this frequently, it could be serious and indicate a dying memory chip. But I don't believe that for your case.

Andi
[ONE Original Android Development] Han-Droid:
Well these are the "surrounding lines":

[52258.957486] krait3_acs [mem 0xf90b8000-0xf90b803f]:

[52258.957524] 00000000: 00000000 00000080 00043710 00000000 00000000 403f3f7f 00002a4a 00000011

[52258.957592] 00000020: 30430600 00000000 00000000 00030000 2a000080 0000c444 00003f3f 00000000

[52258.957657] D-cache tag parity error

[52258.957692] D-side CESYNR = 0x0000cd44

[52258.957729] Kernel panic - not syncing: L1 nonrecoverable cache error detected

[52258.957810] [] (unwind_backtrace+0x0/0xf8) from [] (panic+0x8c/0x1f0)

[52258.957883] [] (panic+0x8c/0x1f0) from [] (msm_l1_erp_irq+0xc4/0x254)

[52258.957955] [] (msm_l1_erp_irq+0xc4/0x254) from [] (handle_percpu_devid_irq+0x6c/0x16c)

[52258.958000] [] (handle_percpu_devid_irq+0x6c/0x16c) from [] (generic_handle_irq+0x20/0x30)

[52258.958072] [] (generic_handle_irq+0x20/0x30) from [] (handle_IRQ+0x3c/0x9c)

[52258.958141] [] (handle_IRQ+0x3c/0x9c) from [] (gic_handle_irq+0x24/0x58)

[52258.958209] [] (gic_handle_irq+0x24/0x58) from [] (__irq_svc+0x40/0x74)

[52258.958275] Exception stack(0xc1119ed8 to 0xc1119f20)

[52258.958313] 9ec0: 00000000 00000000

No undervolting.....btw
[ONE Original Android Development] anshumandash:
I am getting these kernel Wake locks on the latest beta 1 kernel for cm12. I am using it with latest blisspop ROM.
[ONE Original Android Development] pa.pn2:
Hey andi.it seems that cm fixed that annoying next alarm track wake lock. Have a look here.

http://review.cyanogenmod.org/#/c/94235/

Can u please include this asap? Thx sir
[ONE Original Android Development] andip71:
In next kernel version, sure.

Maybe tomorrow.
[ONE Original Android Development] EasyGoingXD:
[MENTION=947981]Lord Boeffla[/MENTION] , any news to zzmove already? :)
[ONE Original Android Development] andip71:
ZaneZam wrote this morning, the problem seems to be gone with unofficial cm12.1 of 10.04.

But I think ZaneZam will comment personally on that later.

Andi
[ONE Original Android Development] ZaneZam:
yeah that's how it is atm : http://xdaforums.com/showpost.php?p=60060632&postcount=784 :(

after 6,5h of running ok i thought issue is gone with 1.0.04 build. this is very very strange i get no kernel/logcat crash log nothing just a black screen

and after a reboot via console a nuked art cache (??) soooo the situation hasn't changed... :( might take a while to pinpoint this as i might have to do trial and error

but lets see...
[ONE Original Android Development] ZaneZam:
ok some news (maybe contains a fix!): i figured out that the app power profile setting was activated! i usually have this off, dunno why it went on -> maybe a forced default after a rom update? if i disable it everything is fine/and or if i leave app power profiles on and disable zzmoove's freq limit at sleep via the tuneable "freq_limit_sleep" (give it the value 0)

can anyone confirm this possible fix?
[ONE Original Android Development] Fenvarien:
It seems this behavior is not necessarily related to zzmove. With the same CM build and Boeffla-Kernel using Interactive governor I got this black screen crash with a following forced ART rebuild. Maybe there's something broken in the current 12.1 CM builds?
[ONE Original Android Development] ZaneZam:
oh thx good to know! yes seems so, some recent changes are making troubles. meanwhile (i'm on unoffical 12.04 build now) i was able to stabilize zzmoove by just removing the sleep limit (only that helps), but that was just 30 mins ago who knows how long that stays. i didn't check myself but Lord Boeffla mentioned that some reverts were done by cm team so hopefully this workaround is soon obsolete. :fingers-crossed:
[ONE Original Android Development] andip71:
Not convinced myself, but tomorrow I will put the 4 reverts in which cm team did last week (and reverted out again too).

We will see tomorrow ☺

At least had no single problem at all here with interactive...

Andi
[ONE Original Android Development] ZaneZam:
Yeah after checking the commits I'm also not that convinced anymore, we will see, and if it changes nothing I've already prepared plan b :)
[ONE Original Android Development] alexbk66:
Was working fine with 4.0-beta2. Flashed again 4.0-beta3 and phone locks up again. Using Resurrection_Remix_LP_v5.4.1-20150408.

[EDIT] Was using zzmoove . Will try other governor
[ONE Original Android Development] andip71:
New 12.1 beta kernel

Hi all,

I quickly put beta4 of the CM12.1 Boeffla-Kernel together for you.

Change log as below.

I would say it is too early for a "horray", but at least I am unable to replicate any of the previous zzmoove issues anymore on my side (with beta4 kernel and CM12.1 inofficial nightly of 12.04.15 by CrazyBoy).

So, let's see what your results are.

Version 4.0-beta4

13.04.2015

Update: Updated with latest 4 official CM kernel commits as of 12.04.15

Flashable recovery zip file is now signed, i.e. you can use signature verification in TWRP or CWM recoveries

Minor internal improvements

Ramdisk updated to version of 12.04.15

Cheers

Andi
[ONE Original Android Development] acuicultor:
All seems to be stable again, using zzmove optimal without an issue since the release of the kernel. Great job and better support, thanks lord!!
[ONE Original Android Development] suaverc118:
Yup, zzmove working great with latest Bliss
[ONE Original Android Development] alexbk66:
Confirm that, get the same with beta3. Black screen crash with a following ART rebuild. Didn't have it with beta2.
[ONE Original Android Development] andip71:
That's why we have beta4 already :)

CM reverted some code they put in lately, which I also had in beta3.

Andi
[ONE Original Android Development] joefso:
- calkulin 2.1 with latest stable boeffla cm11s kernel - no boeffla-config

- Greenify

- AudioMix 1013 "solution"
[ONE Original Android Development] GabrielSousa:
with 5.1 kernel, i dont have wifi !!

is just me ?
[ONE Original Android Development] acuicultor:
WiFi working fine here with cm12.1 kernel beta4
[ONE Original Android Development] Han-Droid:
Sorry for going a little ot now...

Since 12s is finally available I'd like to do a super clean installation.

Back on s3 I moved the Rom to the external sd and deleted the whole (! ) phone memory.

On opo there is no external sd and I feel a little insecure.

Has anyone a failsafe solution?

Tia!
[ONE Original Android Development] :
[MENTION=947981]Lord Boeffla[/MENTION]

I know its too early to talk about CM12S, but just wanted to mention.

I just updated the phone with CM12S OTA, with Boeffla Kernel version 3.1 it starts giving FC in settings, like in display & lights and bunch of here and there.
[ONE Original Android Development] andip71:
Of course. There is not yet a CM12s compatible Boeffla-Kernel out.

And I will only start providing it after Calkulin released his Full version to be flashed. I am not messing around with OTA.

Hope he will be able to work on it soon.

For CM12s, you have to use the stock kernel for now - or other custom kernel when it supports CM12s already.

Andi
[ONE Original Android Development] andip71:
Do a full Nandroid backup, copy it to your PC via usb. Then you should be absolutely safe.

That is how I will do it too.

Andi
[ONE Original Android Development] acuicultor:
No fc here, all seems to be stable and perfectly working
[ONE Original Android Development] andip71:
Interesting, so the Boeffla CM12 kernel seems to work on CM12s?

Surprising, but good.

Still I will provide a dedicated CM12s optimized kernel once I can flash the rom as well.

Andi
[ONE Original Android Development] GabrielSousa:
i had to roll back to beta3 to have wifi :(
[ONE Original Android Development] Renosh:
People have flashed from CM12, CM12.1 and Oxygen OS directly to CM12S via TWRP seems to be a painless process
[ONE Original Android Development] gondsman:
The kernel boots on CM12S, but I don't think it's fully compatible. Display settings for example FCs on a clean flash of CM12S + latest beta.
[ONE Original Android Development] andip71:
It seems, CM team is about to rollback the new wifi drivers again.

So they might have been not ideal.

I am prepared to follow that asap when it passed their code review.

http://review.cyanogenmod.org/#/c/94506/

Andi
[ONE Original Android Development] andip71:
Ok, after download finished I just realized, it is apparently not an OTA but a full install.

I will give that a try soon.

Andi
[ONE Original Android Development] GabrielSousa:
manage to get more info about WIFI,

with beta4 and INTERACTIVE wifi works

with beta4 and ZZMOVE wifi dont work
[ONE Original Android Development] andip71:
Like it??

Hi all,

I guess you could like that? :D

Andi
[ONE Original Android Development] EasyGoingXD:
Give it to meeeeeee :D

PLEASE ^^