yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] kodora:
Xda Should change the name of these forums from XDA-Developers to Xda-complaints, demands and what not.. Good were the times where coming here was to learn and help develop good and FREE Android. Now it's all about cry babies complaining and demanding. People easily forget what the developers here spend of they're free time to give us some goody goods so that our devices don't feel obsolete in a few months.

Luckily there are still a few people like me that are thankful for developers like Lord Boeffla, Zanezam and others!
[ONE Android Development] Timmmmaaahh!:
Thank you, Laura, that was indeed a good read! It also confirms that there

can

be a significant impact by choosing the right governor. I've been trying numerous types with Boeffla and so far Lionheart gave me the best results, even though this one isn't even focused on battery saving (I realise this is very personal and will be different for every user). Now, in the article you so kindly linked to, there's a link to an even more detailed post on getting freaky with Interactive, something I'll have to get into later on (thanks again, Laura).

Duly noted!

As I see it, this is another prime example of confusion resulting from Google and their somewhat unfortunately named system elements (sdcard, anyone?), in this case – snippet from the article – "showing “kernel” as the major source of drain". On the other hand, such vast and diverse operating system is bound to have some misconceptions and urban legends evolving around it.

Despite the incentive being a nonconstructive complaining user (IMHO), I surely learned from this tiny discussion. All negatives have a positive! :D Thank you very much for your input.
[ONE Android Development] kurtextrem:
I can also recommend Smartmax_EPS. Been using it since years.
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.0-beta16-Lineage14.1-bacon

...uploaded!

Changelog:

- l631 build added which is build with a more recent and pure linaro version (recommended!)

credits and thx to [MENTION=6842057]The Flash[/MENTION] for his pre-build toolchains and thx to [MENTION=5331708]laura almeida[/MENTION] for pointing to it and testing!

- nethunter addon packs updated to state as of 29.05.17

enjoy!

ZZ
[ONE Android Development] Ninnix96:
Thanks, but I can't find a mirror or repository. Where I can find all version?
[ONE Android Development] bdwilk:
For LOS-

http://kernel.boeffla.de/zanezam/linaro/bacon/cm14.1/test/

OR-

https://xdaforums.com/oneplus-one/d...-kernel-linaro-sabermod-t2910357/post56117026
[ONE Android Development] Ninnix96:
Thanks!
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.0-beta17-Lineage14.1-bacon

...uploaded!

Changelog:

- l711 build added which is build with linaro gcc 7.1.1 version

again credits and thx to [MENTION=6842057]The Flash[/MENTION] for his pre-build toolchains

enjoy!

ZZ
[ONE Android Development] Ninnix96:
What are difference between all this version? I know the difference between kernel + NetHaunter and without it, but I don't know what rappresent the number of built.

Esample u701, u710, l541...

Can someone explain it? And what version are suggested?
[ONE Android Development] Fenvarien:
These questions have been asked in this thread numerous times. Please use the search function and read the first post.
[ONE Android Development] ZaneZam:
the differences are the used toolchains (and sometimes slightly other flags between builds)

the u* ones are build with Uber toolchains and l* ones with Linaro ones. the numbers are the version

of the corresponding toolchain. recommended is the one u like the most after u tested it :)

but differences are not much actually. personally i like the l711 one the most which is at the same

time also build with the most recent toolchain version. but just try them out maybe "yours" is another one

u can flash over like u want btw. ;)
[ONE Android Development] Ninnix96:
thanks so much, i start from it l711
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.0-Lineage14.1-bacon

...uploaded!

enjoy!

ZZ
[ONE Android Development] Timmmmaaahh!:
Cheers! But wait, moved to stable.. what changed? O_o
[ONE Android Development] ZaneZam:
literally nothing :)

its the same version then the last beta : http://kernel.boeffla.de/bacon/boeffla-kernel-cm/cm14.0/changelog.htm
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.1-beta1-Lineage14.1-bacon

...uploaded!

Changelog:

- Uber v5xx and higher images build with recent toolchain version 20170615 (again thx and credits to [MENTION=5169465]DespairFactor for the pre-builded toolchains[/MENTION])

- u711 build exchanged with u701 which is build with gcc v7.1.1 now

enjoy!

ZZ
[ONE Android Development] Paradox:
Thanks [MENTION=3279788]ZaneZam[/MENTION] for your awesome works, my opo is still rocking with your kernel having 5hrs SOT. More than enough for a three years old mobile :fingers-crossed:
[ONE Android Development] HannibalLecter:
yes. Reporting here is good. Use this kernel with any half decent ROM and you will reap benefits. Not bcz of the ROM but bcz of the kernel.

Hope you understand how things work.
[ONE Android Development] Paradox:
I do understand how things work. It's about the combination. Thanks btw.
[ONE Android Development] HannibalLecter:
yes. The ROM that you used is a very good ROM and combined with excellence from boeffla and zanezam it becomes great.
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.1-beta2-Lineage14.1-bacon

...uploaded!

Changelog:

- Linaro 7.1.1 images build with recent toolchain version 20170702 (again thx and credits to [MENTION=6842057]The Flash[/MENTION] for the pre-builded toolchains)

enjoy!

ZZ
[ONE Android Development] Beep-Bop:
Which variant do you prefer yourself?
[ONE Android Development] ZaneZam:
normally always the latest stable gcc variants which was long time u/l6.3.1 but gcc u/l7.1.1 released recently as new stable

i mostly used uber variants but lately found more love for linaro so the result would be the l711 for now ;)
[ONE Android Development] Timmmmaaahh!:
Exactly the one I'm using! While you're at it, care to share your profile? I know there's a sharing thread here but that's pretty much dead and I'm sure the profile you posted on 23 February 2015 doesn't quite match the one you're using today =)
[ONE Android Development] Nichie:
Why Linaro over Uber?
[ONE Android Development] ZaneZam:
yes but i think i might "disappoint" u as not much has changed it's even more lean now. i use "zen" for sure and nowadays on the opo (as this is long time just a dev device) "zzmoove optimal" with native-hotplugging.

that's it :) well ok one thing i do on all devices is rise the entropy values by factor 2. ;)

btw. Timmmmaaahh (hard to type correct but i did it! yeah! *g*) i guess u read about the freeze issues someone had in official thread. so i have a question: do u maybe face them too with zzmoove on your current setting or do u use another gov? i started to work on zzzmoove snapdragon again yesterday (after 2 years *g*) and found a little bug (which funnily is connected to what i wrote about the thermal tripping in the post u linked) which could be related. BUT after fixing this "someone nice" still got reboots when using zzmoove (logs don't shed light unfortunately). now i consider to do a bigger test with more people (=more logs=maybe more infos). i had freezes and reboots too but since disabling thermal tripping not anymore (for some hours yet). anyways we also got wlan driver related instabilities in some situations lately so this played a role too even governor independent. i think they are fixed with recent LOS kernel/rom changes but i actually don't know yet. all pretty "unsharp" and funny that after such a log time things get suddenly shaky and keep me on the go again :)
[ONE Android Development] ZaneZam:
because it feels noticeable snappier, but that's up the observer and his subjective impression. ;)
[ONE Android Development] Timmmmaaahh!:
Actually, I was still using zzmoove until I clean flashed two days ago because things were getting awry. Honestly, I didn't even consider the governor and I still doubt it would've been the culprit. Thing was, I couldn't get Play Store to boot anymore, kept instantly FC'ing. It did keep updating stuff, like iYTBP, the son of a b**ch, lol! Then the weirdest thing happened: I went to Settings > Apps > Youtube > Uninstall, hoping it would uninstall the update, but it actually uninstalled the entire thing. I never managed to uninstall a system app via 'Apps' before...

I cleared Play Store's cache, cleared its data, flashed Gapps again and dirty flashed ROM, to no avail. That last one caused infrequent random reboots.

I'll attach the Play Store FC's and the kmsg I snatched after one of the random reboots, maybe you can see something, I didn't understand why it was happening. Clean flashing solved it, of course. I don't really see how a governor could cause FC's on one single app but you never know, Android does work in mysterious ways :silly: I'm pretty sure that zzmoove didn't cause reboots, that was on RR stock.

Thanks for the profile update!
[ONE Android Development] Timmmmaaahh!:
For OPO that should be the following...

Threshold read: from 64 to 128

Threshold write: from 128 to 256

... right?
[ONE Android Development] Beep-Bop:
Every single Zzmove profile leads to a freeze in turn a crash

Ps: would attach logs later.

Edit: been using it on aosp
[ONE Android Development] ZaneZam:
actually i mean i tap two times hehe so its 192 and 256 :)

yes please, and immediately crash or after some time using? ok but well i see some more have that, maybe can one with the troubles try to use that kernel

which has thermal tripping removed which i suspect to be the culprit: https://www.dropbox.com/s/e8e4iw9j8...2017-07-05-090723-anykernel.recovery.zip?dl=1

https://www.dropbox.com/s/tqhrgf8xe...5-090723-anykernel.recovery.zip.checksum?dl=1
[ONE Android Development] Beep-Bop:
With test kernel, attached

With official kernel, link

https://ufile.io/q73n3

Edit: Em on aosp, oops.
[ONE Android Development] Timmmmaaahh!:
Good morning [MENTION=3279788]ZaneZam[/MENTION]!

You're right, the thermal thing is tripping! ^_^

Yesterday I flashed the 6.1-beta2-l711 build again on a clean flash. After setting up the kernel profile (details below) I experienced 3 random reboots during any random action. I just saw the screen froze for about 3 seconds and then the 1+ logo popped up. After those reboots I flashed the 6.1-beta2-u711 kernel provided in your recent post and there's been no reboots since. Additionally, I also had some FC's on about 3 apps (iYTBP was one of them, had to clear its data to get it to start), they are not appearing anymore either. Battery use on this profile while screen is on isn't very friendly by the way, nearly 20%/h. While screen is off, on the other hand, battery use is exceptionally great, a consistent 2.2%/h.

Profile

Governor: zzmoove

Governor profile: zzmoove - optimal

Internal SD: zen

CPU Max frequency: 1958 (I think this was at 2457 during the reboots)

Hotplug profile: zzmoove native default

Entropy settings

Threshold read: 192

Threshold write: 256

Everything else is untouched.

Three kmsg's attached, time formatted as YYYYMMDD-HHMM
[ONE Android Development] ZaneZam:
thx man that's an error report! like straight out of the textbook :)

also thx for the logs even tho the included info is as random as the crashes itself. but i'm use to that "yeah finally a log, slobber, slobber" then "oh crap nothing in it to use" that happens often. but the chance still lives that there is something useful in it so its not bad to check it. anyways great that we stabilized that thingy and yah the thermal trpping tripped indeed *g*. it worked quite good back then on older roms/kernel base but i think in newer roms (starting with N) there is another thermal management "in the way" but well thats just a quick impression after checking logs i do not plan to fix it sooo anyway *g* i think we don't miss that "nice to have" if we just toss it. ;)
[ONE Android Development] Beep-Bop:
zzmoove hotplug?
[ONE Android Development] andip71:
Am I right, you use another kernel tweak app and not Boeffla-Config?

Other apps are not supported and can show lots of crap as you can see.

Only Boeffla-Config is fully aware of all kernel features of Boeffla kernel.

Andi
[ONE Android Development] Beep-Bop:
You are tad right, using ya app now and it's fixed.

Btw, get a better picture of yourself, old man

Beep-Bop
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.1-beta3-Lineage14.1-bacon

...uploaded!

Changelog:

- Linaro 7.1.1 images build with recent toolchain version 20170707 (again thx and credits to [MENTION=6842057]The Flash[/MENTION] for the pre-builded toolchains)

enjoy!

ZZ
[ONE Android Development] KuldeepShivankar:
Help Needed.

Hello guys.Just a noobie question.I'm on Sultanized Unofficial RR rom.Can i flash LOS14.1 Boeffla Kernel in it? I want better battery backup. Please help me. :)
[ONE Android Development] Paradox:
Nope, you better check neon kernel for sultan.
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.1-beta4-Lineage14.1-bacon

...uploaded

Changelog:

- Uber images build with recent toolchain version 20170730 (thx and credits to [MENTION=5169465]DespairFactor[/MENTION] for the pre-builded toolchains)

- u631 exchanged with u641 build

enjoy!

ZZ
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.1-beta5-Lineage14.1-bacon

...uploaded

Changelog:

- Uber images build with recent toolchain version 20170805 (thx and credits to [MENTION=5169465]DespairFactor[/MENTION] for the pre-builded toolchains)

- Linaro 7.1.1 build with recent version of pre-build toolchain of [MENTION=6842057]The Flash[/MENTION] (thx and credits)

enjoy!

ZZ
[ONE Android Development] storm119:
[MENTION=3279788]ZaneZam[/MENTION]

Hi zz...after flashed the Boeffla-kernel-6.1-beta5-Lineage14.1-bacon-u641-2017-08-07-195845 since the last 2 days i juz noticed this today i'm getting the u494 instead of the u641 (see ss). Do you aware of this...?

And [probably a bit OT]...after this commits d97d74e76a5c9a3e76201e994aa2e8d79c5a6098 merged...i can't compiled ROMs with UberTC 6.x....always failing and throw errors (see log attached). Should i revert the *ion.c*...any ill effect if i revert only this (ion.c) ?. Plzzzz throw some shed of light or some insight on this issue. FYI...i'm pulling my hairs and banging my head for 2 days now to try to solve this issue...:p

(for the record...i've less knowledge and real amateur once comes to solve the kernel side issue... :D)

Thank you and your help on this matter are really appreciates...
[ONE Android Development] ZaneZam:
indeed!

hi storm119,

thx for pointing, indeed my script tripped (damn again?) when building all the stuff automatically. no i didn't notice.,will check that asap.

and for the error u have two possibilities 1.) fix that line 706 "if (!handle->user_ref_count > 0)" via using that "if (!(handle->user_ref_count > 0)) or "if (handle->user_ref_count <= 0)" 2.) compile with -Wno-logical-not-parentheses flag. i would go for the 1.) even tho i used the 2.) because of "less time isses". explaination: higher toolchains (i think it's since 5.x) are more sensitive to code flaws and u get this error because it's a forbitten warning. not a big error but u should take care of. toolchains < 5.x doesn't "care" about that yet. The problem here is that operator "!" has higher prio then "()" so the handle->user_ref_count get's first converted to a boolian type and then compared if it is greater then 0 but i think the intention was to check if the whole integer comparison is not greater than 0. on later toolchains u even in addition might get a forbitten warning here that a int comparison with a boolian always is 0. i think code will still work as internally boolian uses a integer type but well here my knowledge get a bit foggy ;) anyway we usually should beleve what the toolchain complains so i think it's not that bad to really fix it. but anyway the fast way is to compile with the mentioned flag then the forbitten warning is gone.

that was a bit more light now, hope u didn't got dazzled :)

cheers

ZZ

EDIT: fun fact -> this error is exactly why my script tripped as it jumped over the missing (failed build) so i'm already rebuilding and i meanwhile did add the fix to all branches -> https://github.com/zanezam/boeffla-kernel-cm-bacon/commit/f5ca026a8c706c77ab72b0f5c6a92ae9894ee8b2
[ONE Android Development] storm119:
Holly ****!!!...you're the life saver...thx man. FYI... i choose the method 2 instead of the 1 which i don't want to mess (there is a reason why LOS added that stuff i believed ) with the code rather than want to avoid or get rid or disable the *additional forbidden warning* **** thing....LoL

Ps- I did track your git (kernel) and ROMs was compiled fine (after doing as above method 2) but some how the boeffla_config wont recognise the kernel....i believed this script bbuild-anykernel.sh for stand alone zip (build wont call the scripts unless if i were to build the stand alone flash zip) and i need another method so that the compilation will *tag* the kernel as boeffla kernel....and hence how to make boeffla_config app to recognise the kernel bake-in as boeffla kernel...?. Throw me another light....plzzzzzzzzz :D

Thank you...again
[ONE Android Development] laura almeida:
Make sure the Kernel version string starts with "Boeffla-Kernel"
[ONE Android Development] storm119:
Thx...laura. FYI...I did that before (tried changed on both Makefile or boeffla_defconfig) but still no joy.... :(

Edit: any other suggestion might help me on this...thx
[ONE Android Development] Paradox:
Are you using this kernel with your aosip builds?
[ONE Android Development] storm119:
Yep...with some flag optimisation but those on UberTC/clang side....;)

Edit: lemme correct my above statement....lol. Basically i used different flag optimisation vs ZZ (flashable zip) while compiling both ROMs/Kernel...
[ONE Android Development] ZaneZam:
u wasn't able to change it or u changed it and tha app still doesn't recognise the kernel?

i talked to Lord and he said basically if u name it "Boeffla-Kernel" and put all the scripts and other

ramdisk changes in place (like it is done in the anykernel installer) then i should work.

otherwise u can provide the bc.log file in boeffla-kernel-data folder maybe we can find

something what is missing.
[ONE Android Development] ZaneZam:
all builds fixed and re-upped! again sry for the mess :)
[ONE Android Development] storm119:
I can named it to Boeffla-Kernel (i did tried it via Makefile and boeffla_defconfig) but still the boeffla config app wont recognise it once i boot up to system. Anyway lemme try to compile the ROMs again and try to grab the bc.log...

Thx again...zz :good:

edit: ahh... i forgot and thx to [MENTION=947981]Lord Boeffla[/MENTION] for taking his time on this matter too....:good:
[ONE Android Development] storm119:
[MENTION=3279788]ZaneZam[/MENTION]

Alright....good news i think i know the real culprit (after looking at the bc.log + your git's structure and the boeffla flashabe zip). Boeffla config apps wont detect and treat the kernel as foreign kernel due to the app need all the boeffla's scripts + ramdisk (ramfs) stuffs and this stuffs is missing if compiled inline with ROMs/Kernel. AND the bad news is as i mentioned earlier when comes to kernel side...that is beyond my knowledge. Dunno how to place this stuffs and call by the build while compiling ROMs and repack it as ROMs flashable zip. :(

edit: owh...well at least my ROMs had boeffla kernel bake-in ;)
[ONE Android Development] Paradox:
Why don't you post your roms here at xda? I got your builds from afh ;)

I figured out it's better to look at afh for updates and roms rather than xda :p
[ONE Android Development] ZaneZam:
yah as expected it must be like anykernel prepares it. i unfortunately can't further help in that area as there is 0 experience saved in my head about that *g*

but u surely will find a way. surely not the first custom kernel in a rom build, i guess?
[ONE Android Development] storm119:
Haha...even i don't create a thread or post at xda but still you can found it...right ?. TBH....i really happy that you used my ROMs...:good:

You're right ....but things is bit different if those custom kernel had it's own apps to tweak all the settings. Most of custom kernel out there use the Kernel Adiutor (or KA-Mod) to tweak the settings. And since i'm married with Boeflla Kernel...i thought i'd rather include/bake-in Boeffla Kernel so user can enjoy and feel the power of this kernel but it so unfortunate Boeffla config wont detect the built-in kernel...although they can install KA-Mod but KA-Mod can't unleash the real goodies on Boeffla Kernel...

Ps- Thank you for taking your time to answered all my questions...really appreciates ;)
[ONE Android Development] storm119:
[MENTION=3279788]ZaneZam[/MENTION]

Hi ZZ sir....since i don't find a way or figure out (yet) how to include all the necessary files which need it by boeffla config app on my ROMs. I thought the easy way juz create a separate flashable zip. I'd pulled the kernel/dtd image from my ROMs and used your's flashable zip added the images and flash via recovery....bingo! finally boeffla config recognised the kernel...wooaaahhhh :victory: .

As a side note...I was running this kernel + my ROMs for many many hours now and didn't find any issue...it's run smooth as i want it to be. Before i pushing to my public folder (AFH) would you mind if i use your flashable zip...? (hence im asking a permission here :D)

Ps 1- All credits goes to Mr.ZZ for the kernel source + the flashable zip...i juz compiled the kernel inline with ROMs with some optimisation flags

Ps 2- Credits also goes to [MENTION=947981]Lord Boeffla[/MENTION] for keeping/maintaining the Kernel for bacon

Ps 3- FYI...i didn't do stupid thing like pulling my hairs or smack my head to walls this time...LoL
[ONE Android Development] Paradox:
Great!!! Waiting for the afh link :D
[ONE Android Development] ZaneZam:
Fine u got it working, bravo. Sure go ahead as long as u give proper credits all is good.but just to be super correct u actually should ask Lord Boeffla for permission not me ;)
[ONE Android Development] bkr32:
would this work on Paranoid Android?
[ONE Android Development] Бахрам Байрамза:
No... Camera not working....
[ONE Android Development] bkr32:
wanted to make the jump to PA can't get pa's kernel to build with NH patches so came looking for one :D
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.1-beta6-Lineage14.1-bacon

...uploaded

enjoy!

ZZ
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-6.1-beta7-Lineage14.1-bacon

...uploaded

enjoy!

ZZ
[ONE Android Development] ZaneZam:
looks pretty "chrashless" to me, hmm do u realy had a reboot or "just" a forced framework restart? such a restart looks similar and even shows also the bootanimation.
[ONE Android Development] Aavion:
looks pretty crashless to me, too...

no, phone gone straight to boot-logo, before the boot animation started... and had to enter my pin again. was browsing in chrome, tapped on an image to magnify it, bam! 2-3 seconds lag and then vibration and bootlogo...

had that kind of reboots on my old nexus 4 too from time to time.. there it was the battery monitor chip resetting the phone because of unstable voltages... i hope it's not the battery :/

Gesendet von meinem 1+ One
[ONE Android Development] ZaneZam:
Beta 10 builds!

Hi Guys,

new linaro/sabermod builds of recent 2.0 beta 10 kernels uploaded!

before the question pops up, yes no special build (for CM11 nightly 01.11.14)

yet, not sure if i can do that short-term (not much time atm) lord boeffla did a rebase

in his CM11 repo so i have to look into it deeper. meanwhile consider to change

to a more recent rom :)

enjoy!

ZZ