yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] ZaneZam:
well even though that it should not make that big difference, i read the rom was made with Uber 5.2/6.0 so stay close (that would be my preferred method ;) ) and use either uber 5.2.1/5.3.1 or the 6.0.0 (experimental) one but i would suggest to use the 5.x.x builds as they are more stable (for my experience) but at the end for "the best" u actually only can try them one by one and see. ;)

and btw. yes as time went by things have grown here with all the builds and in the near future i will do us all a favor by reducing the amount of builds. :)

which ones will be dropped isn't decided yet (for example i think the versions starting with 4.x.x are obsolete, aren't they? *g*) and might also be decided via a poll then, i will see... but for now i'm sry for spoiling u for choice, sometimes i'm also getting confused a bit when testing/uploading stuff *g* but well that might also be related to "getting old" :o
[ONE Android Development] ZaneZam:
ok thx, meanwhile i've checked all the mirrors and from my point of view all images seem to be fine on the server. normally the main server (on lord boefflas host) doesn't make big troubles (at least not for my experience) with render server i'm not sure there u might run into some file re-syncs between us/eu servers were files are not 100% transferred. i'm using the eu one for my region. so it has to replicate stuff to us servers. but well fortunately i have alternatives and u got your desired one, enjoy! :)
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-5.0-beta21-CM13.0-bacon

uploaded!

enjoy!

ZZ
[ONE Android Development] P1nGu1n_:
Have been using the uber 6.0.0 ones since its first release (CM12?) and they've always been super stable to me, just so you know :)

Thanks for your builds, I always flash a fresh nightly and the u600 build when you update them! :good:
[ONE Android Development] laura almeida:
[MENTION=3279788]ZaneZam[/MENTION]

Are you alright ?

All of a sudden no response from you!!!
[ONE Android Development] ZaneZam:
Sure my dear I'm fine, still writing on the reply pm to You so u will even get a massive response, be aware! :)
[ONE Android Development] Aavion:
Got random reboots ~once a day while scrolling/browsing a lot. Using COS 12.1.1 and the latest l5xx kernel built by you. Also had this problem before the latest OTA, also using the linaro 5.x kernel (4.1/4.2)...

Phone just stops responding and after ~30 secs it reboots itself. I captured the last_kmsg everytime and everytime the bottom lines look like these attached...

do you think that this could be kernel related?

the problem doesn't show up if i'm not doing a lot of stuff in a short time :D it's not easy to reproduce, but today i flashed the original kernel by andi and it hasn't rebooted yet....
[ONE Android Development] ZaneZam:
hmmm looks like kernel related but difficult to say without more information but as u are using the official build w/o freezes, tendential yes ;)

i'm more using the Uber builds and especially atm the u521 since weeks and 24/7 without problems. i think i did no long term tests with the l521 ones

but i never had any reboot with any of the builds before uploading (after fixing them if there were any eg. at the boot process *g*) otherwise they would not be available. ;)

BUT that doesn't mean that u do not have problems with some or even all of them on your system. to be honest with these builds everything is possible! ;)

ok now what i can do is to suggest u to try the Uber 5.2.1 build and/or i can "earlier than planned" provide a updated image build with linaro 5.3.1 toolchain

(Boeffla-kernel-4.2-beta1-COS12.1-bacon-l531-2016-01-10-232325) this toolchain is self made and a developer snapshot so not a release version but with this toolchain i did long term tests with two devices with CM13.0 systems (shaky per se *g*) and they run/are running rock stable for me.

BUT that not daily stressed and with lean configurations ;) so hopefully u get a stable system back with either of these suggestions.. good luck!
[ONE Android Development] Aavion:
flashed the l531 version and it feels snappier than l521 and much snappier than original build :) i can also say that the audio delay caused by maxxaudio is noticable better now and haptic feedback is more accurate... and that just after testing for a few minutes now :D and it's not just placebo, as i can directly compare these builds.

speed and snappiness feels like i'm not using cos anymore :D i hope, my problem is also solved now, but it needs at least one or two days of testing 'cause i cannot reproduce these freezes, as they're random and happen only during very ram-intensive scrollings (like fast-scrolling facebook for a while) and not everytime...

i' ll keep you updated about my experiences with the new build, but the first look is very surprising ;)
[ONE Android Development] ZaneZam:
New Build!

fine that sounds promising, then this build might be "yours" :fingers-crossed:

ok then we gonna make this "official for the others" too :)

as mentioned additional build of...

Boeffla-kernel-4.2-beta1-COS12.1-bacon

uploaded!

Changelog:

- added l531 image build with linaro snaphot gcc version 5.3.1 2015.12 (own customized toolchain)

enjoy!

ZZ
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-5.0-beta22-CM13.0-bacon

Boeffla-kernel-4.2-beta2-COS12.1.1-bacon

uploaded!

enjoy!

ZZ
[ONE Android Development] Starsream88:
You mean beta22 [emoji1]

Envoyé de mon A0001 en utilisant Tapatalk
[ONE Android Development] ZaneZam:
yes thx corrected! copy + paste + too late here :)
[ONE Android Development] Aavion:
Testet l531 build for some days now and didn't had a single problem, except gaming performance in some games (eg Death Trigger 2 on maximum settings). But these games also lag on stock kernel, so i think cyanogen messed something up with 12.1.1, since before that update everything was fine :D

so freakin' rock stable ^^ thanks again.

E: Just had another single reboot . But the kmsg looks completely different than the others I posted last week. So I don't think that this one is related to those random reboots I once had which were solved by using another build.

My config: no oc/uv, zzmoove moderate, zzmoove native hotplug, everything else stock, custom lmk config, integrated superuser, no other root apps (only bc and terminal).

only change: facebook app updated last night and at first use "bäm, reboot" :D don't know if that's related but maybe you've got an idea [MENTION=3279788]ZaneZam[/MENTION] :D

E2: It seems to be related to the Facebook app, as some others have similar problems with their phones since the last fb update, too, which were solved by uninstalling the app or updating to beta channel (which has other problems xD). But this only seem to affect CM and TW based phones/roms... I've reportet this behaviour to Facebook with full logs attached. Maybe they'll figure it out :D
[ONE Android Development] suaverc118:
Beta 23 is out. Zane, thanks for all your hard work. Looking fwd to the next build.
[ONE Android Development] ZaneZam:
New Builds!

yes had to do some service on my build machine before i could build again. ;)

so a bit delayed here it is....

Hi Guys,

builds of...

Boeffla-kernel-5.0-beta23-CM13.0-bacon

uploaded!

Changelog:

- u600 build with older version 20151101 of toolchain as latest source changes broke the usage of newer u600 tc-snapshots

enjoy!

ZZ
[ONE Android Development] suaverc118:
What do you use?
[ONE Android Development] ZaneZam:
meanwhile usually u531 ones on all devices. but for testing and because these are the "most sensitive" ones i end up using the u600 to see if they keep stable long term.

but honestly i'm switching too often, all i can say is that i often finally come back to the u531 builds they feel the best for me, its not much but for me noticeable. and just for the record

i'm not so much into "best battery live" any more so that build might not be "the best" for guys who want that. but i actually don't know maybe it even is ;)
[ONE Android Development] suaverc118:
Lol, sorry, I meant what do you use to build since you were having trouble? Also kernel wise I use l531 and love it
[ONE Android Development] brisac:
Think l531 is best for battery life or u600?
[ONE Android Development] Mrcactuseater:
Most likely l531, u600 is more performance driven

Tapatalk'd from my Twisted, Blu-spark'd Nexus 5
[ONE Android Development] Aavion:
i'm really happy with l531, i'm at 16% now with 5.5h sot :) (cos12.1.1)

Gesendet von meinem Schinken.
[ONE Android Development] ZaneZam:
hi guys,

luckily i managed to also "bring up" the u600 build with newest uber 6.0 toolchain veery early today with the result as attached. is this good guys? sounds dumb but i can't say it

as i'm normally do not look at the result (just doing stab tests) but this time i had a feeling that it might be higher than previous results, just a feeling? :) anyway will give

it another few hours and then exchange it with the existent one if it keeps running stable. ;)
[ONE Android Development] TorchaOne:
Gimme! U600 was the best I used do far anyways...
[ONE Android Development] ZaneZam:
ok ok! :)

Hi Guys,

as stated u600 build updated to

Boeffla-kernel-5.0-beta23-CM13.0-bacon-u600-2016-01-18-235255.recovery.zip

Changelog:

- build with Uber gcc version 6.0.0 20160110

- enable -Ofast again

- fix ICE with Uber gcc version 6.0.0 20160110 by removing graphite optimizations

- fix not booting device by disabling tree vectorization and vectorize with neon optimizations

(-ftree-vectorize -mvectorize-with-neon-quad)

enjoy!

ZZ
[ONE Android Development] blinoff82:
First time for everything while i use your kernel, I received such a warning:

ROM - CM13 official nightly 20.01.2016

UPD: I do not know whether this can be the cause, but I use SuperSu, Xposed and Busybox by Stephen (Stericson).
[ONE Android Development] ZaneZam:
hi blinoff,

well supersu, xposed and busybox per se shouldn't make any troubles (in fact i have them all running here on cm13 in different combinations for testing)

but maybe it's a xposed module which is restricting access to your storage? xprivacy installed ? the mightiest of them all and actually the only one

which i know that can bring u in troubles :)

btw. just installed current nightly and cannot reproduce that problem so it might be something special on your system maybe u can try to disable

xposed/modules of it and remove supersu/busybox or in short dirty flash latest nightly :) if u don't need supersu/busybox i anyway would recommend

to use build-in ones su by rom and busybox by kernel. but again they both do not cause restricted access to your sdcard. ah one thing and the most important

one pops up at last in my mind -> the app security settings in cm13 might be "messed up" check if boeffla app has access to your internal storage enabled!

gluck :)
[ONE Android Development] blinoff82:
Hi ZZ! Just report: clean flashed todays nightly + your latest kernel (U600). I do not install third-party SuperSu, Busybox & Xposed. Works without problems. Thx for feedback. ;)
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-5.0-beta24-CM13.0-bacon

Boeffla-kernel-4.2-beta3-COS12.1.1-bacon

uploaded!

Changelog:

- Uber images build with recent 20160110 versions

- fixed boot with u600 build

enjoy!

ZZ

PS: mediafire mirror upload pending...
[ONE Android Development] TorchaOne:
Made a little test, 22th official nightly, governor: zzmoove, profile, battery plus, schedulre, tripndroid, hotplug zz native def.

with "original" boeffla Vellamo gave and / U600 gave

Multicore: 1720 / 1610

Metal: 1015 / 1267

Browser: 2208 / 2295

Best values for last two days testing and tuning are multi/metal/brow 1915/1723/2959 with different profiles and governors... Nothing serious tuning or exact engineering work but just for fun, there is a little something with this U600 build.
[ONE Android Development] kalpik:
He just pushed beta 25 [emoji14]
[ONE Android Development] ZaneZam:
and i just did it too :)

Hi Guys,

builds of...

Boeffla-kernel-5.0-beta25-CM13.0-bacon

uploaded!

enjoy!

ZZ
[ONE Android Development] ZaneZam:
Hi Guys,

builds of...

Boeffla-kernel-5.0-beta26-CM13.0-bacon

Boeffla-kernel-4.2-beta4-COS12.1.1-bacon

uploaded!

enjoy!

ZZ
[ONE Android Development] wimsjohn:
sorry but i don't get why zanezam does those (mirror?) builds? As far is i understand he just recompiles boeffla kernel?

Oh and he does builds for cm...
[ONE Android Development] P1nGu1n_:
I don't think you do understand. He doesn't just recompile them, that would be pointless. He compiles Boeffla Kernel using a number of toolchains. He only makes minor changes to the kernel in order for them to compile against those different toolchains. Builds built with these toolchains might or might not improve performance or battery life. Correct me if I'm wrong Zanezam :)
[ONE Android Development] Fenvarien:
Please read the OP and especially the section "Now some more precise informations about what's going on here".
[ONE Android Development] suaverc118:
Zane is good at what he does and their are differences with his builds. And when he runs into problems, he has to fix those issues, its not like he cuts and pastes the builds. We can thank him for zzmove as well. He puts work into a lot of this
[ONE Android Development] molonad:
hello mistr zanezam :eek: i have a question for you :) i was for a while on some caf roms , i was on normal cm 12.1 roms and now iam trying normal cm13 roms , but on every cm13 with all your zzmove governors and native hotplug is very aggresive scaling - for example zzmove battery extreme is ramping very fast to max frequeny as same as optimal or performance profile (so it is not really battery friendly). it is weird , i think it didnt work like this on cm12.1. for example on caf builds all governors work different then in normal cm builds. for example smartmax eps should be very battery friendly, max frequeny should not be reached so fast , in caf builds it works like it should but in cm normal builds it again scale fast to max frequeny. Can you tell me if it is normal ? thank you
[ONE Android Development] ZaneZam:
nope i sry can't atm. i would have to investigate. but what i already know is that all the profile settings need a very time consuming re-working as i just did a kind of "porting it over" from the exynos to the snapdragon platform back then. so yes it might be that they all are behaving similar, in fact i had the same impression back then all settings almost give the same impression. and yes i guess CAF->normal cpufreq implementation might give also different results, but here we can not do much as this is the point between CAF and "normal" to be more "optimized" for the used qcom SoC. that's just my actual humble opinion, i would have to do a deeper look and doing this is only useful when i have time for it and that's my biggest problem actually! ;)
[ONE Android Development] ZaneZam:
hi wimsjohn,

in short i take the official boeffla sources and compile them with optimized toolchains (linaro/uber/back then sabermod) and optimized compile flags

w/o changing the "good base" of boeffla kernel to much(!), u can call it giving it the "icing" or "den Zuckerguss" if u want :). as some obviously

satisfied users (thx guys for the nice words! :highfive:) already mentioned this can give u more speed/"fluitness" or even less "energy consumption"

beside of that i try to keep the builds up-to-date and running which is as mentioned btw. really often more difficult then u might thought ;)

that's it, finally i wanna say: to know if it's really the "icing" what u get u will have to try it by yourself. these builds are stable but still experimental

and u can only expect 100% stability from the official build (as there is always a stable stock toolchain used).

but it's easy to test just flash over the builds u want it's like a normal boeffla kernel update and all settings are preserved. ;)

cheers

ZZ
[ONE Android Development] wimsjohn:
Thanks for the quick and extensive reply! I'll give it a try ;)

wimsjohn
[ONE Android Development] ZaneZam:
OnePlusX invites!

Hy Guys,

i forgot i've got 3 invites for a OnePlusX

if u r interested they expire in approx. 8h:

http://onepl.us/GL1D-0BAD-92D5-D2F4

http://onepl.us/GLBB-6FF3-CD9E-7E4C

http://onepl.us/GL3C-D047-1A51-509E

Cheers

ZZ
[ONE Android Development] rolarocka:
This kernel is so great, I use it with the jgcaap rom mm at 1267MHz, zen io, zzmove moderate, 960MHz input boost and 330MHz GPU. Everything is snappy, fluid and battery life is awesome [emoji2] [emoji2], ty ZaneZam for this kernel [emoji482].

A0001 - oneplus one
[ONE Android Development] molonad:
Thank you for your answer. Also i moved back to caf becouse I Want to try your profiles with zzmove native hotplug and it is working very well. Same as on lollipop and kitkat times. So if there will not be any change im cm13 and zzmove i Will stick with darkobas and nuclear kernel which have zzmove governor and all profiles and hotplug and it is working very well. Iam happy about it.

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] molonad:
Also Mistr zanezam, sorry to interutpt you again, i found out that if i have msm limiter enabled, and i have for example max screen off frequency configured to 729 MHz and my Phone went deep sleep, then if i unlock my Device i have maximal frequency 729 and i had to change governor to fix it. So then i raised that screen off frequency to 24xx, max frequency and problem was solved, but i had some random reboots, so I completelly turned off msm limiter, now it seems okay. Can you please tell me if there is configurable some hotplug idle Frequency or something like that? Becouse there had to be some conflict which lead to this behaviour.

Odesláno z mého A0001 pomocí Tapatalk

---------- Post added at 11:41 AM ---------- Previous post was at 11:33 AM ----------

Also Mistr Dont you think that People need to know that your profiles Dont work in cm13 as it was before ? Iam so sure about it, but they are blind. Also all interactive and etc governors have really same behaviour, max frequency is really fast reached and it is not right.. And i Dont understand why even Mistr boeffla disregards it.. Iam sure that this governors behaviour is not right and someone should look into all governors and try to configure them again. U think only governors which working like it should I is powersave and perofmrnace.. Smartmax eps which is very powersave and Dont achieve nearly max frequency is on cm13 in max frequevency every time you open app (on all 4 cores), and all governors work like. This. I Dont know if are all blind or iam trainspotter..

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] ZaneZam:
[kind of OT]

well i can't say anything yet.. that needs deeper inspection (pretty difficult topic!!) = more time i have at the moment, much more. and honestly cm13 is not yet settled, so there is everything possible.

they still try to find the "right base". next update from [MENTION=947981]Lord Boeffla[/MENTION] will show that he also had to start from scratch again, thats not so funny. i think we can talk about this topic only seriously if we r

using cm13 for a couple of months (yes seems so *g*) without a changed based from their side (without knowing what exactly they changed, but still). ;) and a trainspotter? well for me it's very positive

that u have envolved that kind of sense here as i'm not able to do long tests and so on. so i appreciate that u have a look and hope u will come up with such reports in the future ;)

but i think atm it's kind of wasting time (hence i even don't try to find time to look deeper. u get me? *g*)

[/kind of OT]
[ONE Android Development] molonad:
Thank you for your answer, you are very kind. Also can you answer me to other part of my question? About idle Frequency? Thank you

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] lokesh.3440:
Which kernel version are u using buddy ? U600 or U521 ?
[ONE Android Development] rolarocka:
U600

A0001 - oneplus one
[ONE Android Development] ZaneZam:
[again a bit OT] *g*

maybe i subconscious ignored that part because i don't know anything about MSM Limiter :) i actually had to search for it with uncle google

as i either never came across or "deleted" this inormation as i usually only keep knowledge in mind which i need or might need :)

ok if that is a special driver (i read something about msm limiter driver) then i have to state that it's not included in boeffla kernel hence everything

which depends on this driver is not supported. if it is an app which do thing on "rom level" then u have to be aware that boeffla kernel has switches

to allow overwrites from the normal (and recommended!!) method of doing it per init process + kernel config. so either try to use these overwrite

switches in app settings or quit using this msm limiter. one thing u can try to use with boeffla or any other kernel which has zzmoove included is

the sleep limit functions of it. they r disabled per default in boeffla kernel via the tuneable "disable_sleep_mode" (0 is enabled ;) ). disabled because

these settings can make troubles when waking up the phone (delays in seconds) or when phone is doing something when screen is off

(playing music, getting notifications etc.) so be aware, but this would be at least an alternative.

[/again a bit OT]
[ONE Android Development] ZaneZam:
Hi Guys,

builds of...

Boeffla-kernel-5.0-beta27-CM13.0-bacon

uploaded!

enjoy!

ZZ
[ONE Android Development] suaverc118:
Her [MENTION=3279788]ZaneZam[/MENTION] how are you? I know you may be able to help some of us. I'm running temaseks ROM and its not booting with the boeffla kernel. Seems that it may be on the ROM side because other kernels aren't booting with it, he's using an uber toolchain I believe. Would you have any idea why it may not boot with his ROM?

Thanks
[ONE Android Development] ZaneZam:
fine thx and u? :)

hmmm well i'm almost sure that it's not the toolchain he uses.

most probably a ramdisk mismatch or anything else which is too

far away from the CM base or "normal" init stuff. but pretty hard

to say without more deeper knowledge or anything to try, sry.
[ONE Android Development] suaverc118:
As always, thank you
[ONE Android Development] blinoff82:
Hi ZZ! Sorry for noob question, but where is your changelog? Can not find link in OP...
[ONE Android Development] ZaneZam:
u mean the changelog of boeffla kernel? as always everything can be found here: http://boeffla-kernel.de/

if u mean my little changelog for my builds here, then: no changelog as nothing changed from my side, this

means last changelog (in the announcing post) still applies.
[ONE Android Development] blinoff82:
Collegues, today"s nigtly (30/01) + latest boeffla U600 (by ZaneZam) = bootlogo [1+1]. Can you confirm this?

Device - bacon.

UPD: Flashed this kernel. Not booted... WTF?! Devs again broke something?:eek:
[ONE Android Development] Fenvarien:
Lord Boeffla announced with beta27 that CM changed a lot in the kernel starting with today's build and that he needs to rebase. Until then newer CM builds will most probably not boot with the latest kernel release.
[ONE Android Development] suaverc118:
Yes, latest 5.1 kernel boots with temasek!!!
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

builds of...

Boeffla-kernel-5.0-CM13.0-bacon (for all CM nightlies up to 29.01.2016!)

Boeffla-kernel-5.1-beta1-CM13.0-bacon (for latest CM nightly of 30.01.2016 or newer!)

uploaded!

enjoy!

ZZ
[ONE Android Development] merikgvr4:
I downloaded that apk already but when I click the apk it says can't install.
[ONE Android Development] Aavion:
you have to enable unknown sources in security settings
[ONE Android Development] merikgvr4:
I always enable that . I am running art. Would that be the reason?

Got it installed. Had to click thru file manager. Thanks.
[ONE Android Development] Aavion:
dunno.. i run dalvik because on art my opo sometimes do sudden self reboots after systemui crashes... maybe it's the theme i'm using doesn't fully support art?! (Veu)

on my s3 the boeffla config app ran well on art...