yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] vurtomatic:
Unfortunately AudioFX still goes into an FC loop after installing Viper on Bacon with latest Blisspop and after using your app to set selinux to permissive. Not sure why but not too bothered since I can live without equalizers.
[ONE Android Development] HaTrED_:
Kinda OT...

First of all, please nandroid yourself mate!

Then, try this zip:

https://www.dropbox.com/s/tiysbob1wlcpkv5/V4Android_v2.3.4.0_katinatez_V1_material_light.zip?dl=0

- Set kernel to permissive,

- Run V4A, install drivers,

- reboot,

- Profit, i hope!

It shouldn't be necessary to change anything at all - namely nuplayer and etc's!

Credit goes all to dev's!
[ONE Android Development] RCT1:
Don't forget to select in settings SElinux permissive after reboot.
[ONE Android Development] smint86:
I'm mostly out of time atm, wanted to report in since days with a longer report but it's not possible. Work...

But in short: Switching back from f2fs-mixed to full ext4 was absolutely worth it. I started with b17 Linaro or so, now I'm on v3.1 Uber 5.0.0 and it's totally perfect together with Temasek Uber ROM.

With very light usage my phone lasts up to four days, with heavy usage (which I don't have time for atm) I can easily go through a day. SOT approximately 5-6 hours. Always while delivering perfectly fluid UI and performance. At the beginning I had a few (below 5) random reboots which stopped when turning off UV.

cpu: zzmoove - battery yank

hotplug: zzmoove native default

gpu: simple_ondemand

touch boost: 1267 mhz

selinux: permissive

rest stock

Thank you very much for this perfect work [MENTION=947981]Lord Boeffla[/MENTION] and [MENTION=3279788]ZaneZam[/MENTION]. I'll stick with this for sure.
[ONE Android Development] vurtomatic:
Thanks dude. Just to confirm, all I have to do is flash this zip file with TWRP in recovery?
[ONE Android Development] HaTrED_:
Yap, but before that perform a nandroid backup! :good:
[ONE Android Development] vurtomatic:
Unfortunately this is still not working, I'll try it some other time ;) Thanks for the file!
[ONE Android Development] XanRules:
Okay, so I'm about to install the most recent CM12 Nightly (cm-12-20150407-NIGHTLY-bacon.zip).

I believe that's a 12.0 nightly, which means that I'd use these "stable" builds: http://boeffla.df-kunde.de/zanezam/linaro/bacon/cm12.0/stable/

Which do I use?

Please explain like I am a small child because stuff like "you'll need to recompile the Uber/Sabremod 5.03.47 Linaro v2 toolchain from the ak kernel repositories within CWM" hurts my brain and the FAQ in the original post has somehow managed to make me even more confused ¯\_(ツ)_/¯

Thanks!
[ONE Android Development] ZaneZam:
oh i like to explain, and now a really not confusing answer: yes that's right! :D

*g* actually u are completely right just use one of the builds from the link u pasted here, easy like that *g*. "one of these" means u can pick one of them as u like they are all the same kernel version just each of them complied with another toolchain. the tag included in the file name means : l493 = linaro 4.9.3 toolchain, u493 = uber 4.9.3 toolchain, u500 = uber 5.0.0 toolchain, "toolchain" is the thing which makes the kernel btw. :) ah and for a rule of thumb: the folders where the images are located are named accordingly so if u for example ever switch to CM12.1 u know where to find the right images ;) and if any of the folders are empty means that there is no such version at the moment so no files in "test" = no test versions available, no files in "stable" = no stable versions available.

hope i "de-confused" u a bit :)
[ONE Android Development] XanRules:
Cool, so regarding which toolchain I use, it doesn't REALLY matter, just personal preference? Download the file and its associated checksum and flash in recovery like any other kernel?

Haven't had a flashable phone for a few years so I'm a little rusty. Thanks again!
[ONE Android Development] ZaneZam:
yes it doesn't matter which one u use till u found the one which feels the best for u ;) and yes flash it like other kernels via recovery (after checking if the zip is good via checksum)

u even can flash over other versions and vice versa and also in case of troubles u can flash over the Original Boeffla Kernel Images if u want or have to.

in addition if u didn't already know i would suggest to use Lord Boefflas Kernel Config App to be able to setup kernel stuff after flashing ;)
[ONE Android Development] HaTrED_:
Cof... Cof...

CM12.1 V4beta3 is out [MENTION=3279788]ZaneZam[/MENTION]! ;):D

[MENTION=3366676]Fenvarien[/MENTION]

Tss... Tss... :p

You're absolutely right mate! It's V4 beta3... damn!

Tapatalked!
[ONE Android Development] Fenvarien:
It's beta3 or you are travelling through time... ;) But you are right, there's a new, tasty beta kernel from the Lord! :)
[ONE Android Development] ZaneZam:
New Builds Up!

:) and now "the other builds" of Boeffla-kernel-4.0-beta3-CM12.1-bacon are also available!

have fun!

ZZ
[ONE Android Development] suaverc118:
The strangest thing with the new build and today's cm12.1 build by crazy boy happened. Double tap wouldn't wake up phone when being charged. Had to unplug it then double tap. Things were moving a little slow too. So I flashed the previous u500 4/2 build and its better. May give another shot but wasn't sure of it was the kernel. Anybody else?
[ONE Android Development] ZaneZam:
damn yes me! :D strange thing yes i in addition get a total blackout after unplugging the charger and i cant wakeup the device. oh bummer ok i guess i have to check whats wrong... at least i will check if it is build related.. ;)

PS: just to let u know: checked! seems like its not build related have the same problems with official kernel, but i talked to lord boeffla and guess what? he has no problems with the same kernel/rom situation hence something rom related and or update method related (?). i did an update today per dirty flash (as always) and nothing special happend so far during/after update. problems started by using a charger/usb connection, no clue what the problem is atm. :(
[ONE Android Development] ZaneZam:
...hence something rom related and or update method related (?)... well completely wrong mr. *g* we found out that the issues are obviously coming from zzmoove (thx to [MENTION=4551715]suaverc118[/MENTION])

don't know why atm. but i will of course take a deeper look. i hate it to say again but please stay away from zzmoove in latest 4.0 beta3 (all builds, even offical!) for now ;)
[ONE Android Development] XanRules:
Hey man, I flashed the Config App (2.1.73) and it's telling me I'm missing root. I have enabled root access in developer options (CM12).

This happens regardless of which kernel or toolchain I flash, all of which have had their MD5 checked.

Any thoughts?
[ONE Android Development] ZaneZam:
I'm using su/supersu from chainfire and I never had a problem. Well if I do not forget to flash it after a rom update. If I do, I get the same problem :) maybe u can give it a try? Therefore I can't say much about the stock root access functionality.
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

just uploaded builds for following versions:

Boeffla-kernel-3.2-beta1-CM12-bacon

Boeffla-kernel-2.6-beta1-CM11-bacon

Boeffla-kernel-2.6-beta1-CM11s-bacon

like in original build these recovery zips are signed now.

enjoy!

ZZ
[ONE Android Development] XanRules:
yeah, I dunno. I've tried flashing the SuperSU zip as well as just updating SuperSU from the play store and nothing. Weird stuff.
[ONE Android Development] NeGriTa79:
I installed yesterday LiquidSmooth and then I put the Kernel Sensei ... And I do not work anymore WiFi ... Even if I put the boeffla ... Nothing ... I was told to flash the zip restore WiFi 38r to solve ... What do you advise me to do?

Resolve... Flash the WiFi 38r restore and flash 2.0beta4 Sabermod... WiFi working...
[ONE Android Development] ak:
This isn't the best solution because liquid is based on CM11.

ak@bacon@pancetta
[ONE Android Development] NeGriTa79:
But I have resolve...
[ONE Android Development] ak:
Yes ... but if you flash another kernel probably your wifi will not work.
[ONE Android Development] Ankit Tulsian:
My phone hot rebooted twice while I was watching YouTube

Here is my log from the app

http://pastebin.com/e90D3SKA
[ONE Android Development] suaverc118:
Mines done that with a YouTube video as well, but only once or twice at the most.
[ONE Android Development] suaverc118:
I just had it happen again when I was taking a picture with upgraded stock camera about an hour plus ago. I think it was in raw mode. I'm also using the latest linaro build
[ONE Android Development] ZaneZam:
even though i dunno give much support here es stated in the OP :

(btw. if someone doesn't know: Lord Boeffla will also refuse any support if people are using UV!) ;)

so guys disable it (assuming u also use it suaverc118 *g*), try without and see. my experience with this device is that it is much more sensitive in terms of voltages and therefore tends to be more unstable

than other devices when uv/ocing (compared to Samsung devices for example) so if u really "have to" undervolt i would suggest to use only light values. -50mV might be even too much here as used by Ankit ;)

in my opinion UV/OC is always a stability lottery and the benefits are in general questionable
[ONE Android Development] Ankit Tulsian:
Thanks ZaneZam. After posting here I removed UV and now it's stable. -50mv worked perfectly on Ak kernel though. Any ways thanks for replying.

Edit: Are you planning to update the kernel with the latest important fixes which Lord Boeffla included in his latest beta?

Regards.
[ONE Android Development] f100cleveland:
I remember from the N5, every kernel would UV different. That phone wasn't nearly as sensitive as this one in.

But the sm/linaro beta 5 will be released soon I bet....
[ONE Android Development] suaverc118:
My phone isn't undervolted. It's also clocked 300-1497 zzmove with zzmove yank.
[ONE Android Development] ZaneZam:
then it might be the build itself, but u only know that for sure if u change to official build, keep your settings and see if it still chrashes afterwards...

but first u and all others might try also the new just uploaded beta5 linaro/cm versions ;)

enjoy!

ZZ
[ONE Android Development] suaverc118:
Question... If I'm trying to get my battery memory/life down by keeping my kernel consistent, will I have to start all over again if I stay on linaro with a new build? They always say give it a few cycles. Does it really matter?I did get good numbers still.
[ONE Android Development] ZaneZam:
i used to suggest these charging circles too in the past *g* because it at least had relevance on some devices back in the days

but mainly after changing a rom actually! honestly i'm not sure any more if this still applies, i think its more a "left over" from that times

especially after flashing a kernel image might be even a complete rumor because for the system it's really just a reboot :) but someone

with some more light into bat stats etc. can surely spent a little spot, personally i don't care much i anyways don't get reliable results

during testing stuff every day ;)
[ONE Android Development] suaverc118:
I figured its more for flashing new Roms but wasn't sure if it applied to kernels over the same ROM that never changes. Especially of its the same kernel but just an upgrade.

Thanks.
[ONE Android Development] Ky0sHiR0:
26.10 version on zzmove + battery plus 300-1574 MHz fiops -25 mV testing now : )
[ONE Android Development] suaverc118:
Let us know.
[ONE Android Development] suaverc118:
Here's what I got with the latest linaro using zzmove/battery yank/300-1497/-25 UV and zen. Not bad
[ONE Android Development] NeGriTa79:
[MENTION=3279788]ZaneZam[/MENTION] you'll come out even the new version of Boeffla ??? I was hoping to try the new Beta7 ...
[ONE Android Development] f100cleveland:
Its being tested right now. Hang tight;)
[ONE Android Development] vurtomatic:
What does recovery refer to? I was confused by the file names.
[ONE Android Development] ZaneZam:
Recovery zips are the ones u download and flash with cwm or twrp. And these zip are now signed and u can now use the "check signature" feature if u want

EDIT: and i forgot u meant the changed filename? yes its a bit confusing at first (happend to me too when i saw them first from lord boeffla *g*) but it's just

a generalized naming now (and a also new build process) as we have also other recoveries then CWM ;) but u dont have to care just flash the files the ususal

way ;)
[ONE Android Development] smint86:
What about using zzmoove with 4.0 beta2? Is this considered safe? I finally switched to CM12.1 (Temasek v9.6) and can't wait to jump on the Boeffla/ZZ-train again [emoji1] . Obviously with zzmoove native setup, my favorite so far.
[ONE Android Development] ZaneZam:
well I was going start a debugging session to find out what the problem is with zzmoove (meanwhile with crazy boy's unofficial 10.04.15 build)

and guess what? the issues are gone and I'm back to normal here :)

strange though but obviously changes in the rom had something to do with it. dunno how up to date temaseks rom is so I can't say it for sure, u just have to try.(nandroid is never a bad idea *g*) ;)

EDIT: sry that was unfortunately a false positive! just tried a normal non debugging version and things are getting stranger only the debug version runs without problems! inverstigating further...

EDIT2: now with the debugging version the same issuse (did run 6,5h before i switches to non debugging version) ok forget all what i wrote, same strange (and not debuggable atm) situation! bummer!
[ONE Android Development] brisac:
So we are safe to use zzmoove governors on 12.1?
[ONE Android Development] ZaneZam:
it turned out only if u set the zzmoove tuneable freq_limit_sleep to 0. I'm running it fine with 12.04 build since a couple a hours with this setting.
[ONE Android Development] brisac:
So battery yank could be usable only from next update?
[ONE Android Development] ZaneZam:
you can use every setting but u have to disable the freq sleep limit before the screen goes off :) every setting has a sleep limit so when u switch u have to do it again. this is for now if the next version from Lord boeffla doesn't fix that problem I will provide a plan b which is simply to disable sleep limit everywhere. but for now we have to do it manually via the tuneable mode.
[ONE Android Development] suaverc118:
How do we do this? When I flashed it when we first had the issue, I didn't mess with anything and when the screen went off, that was it.
[ONE Android Development] ZaneZam:
u have to use the "tuneable mode" on governor tab. that's only available for donation users. first choose your preferred zzmoove profile then choose governor profile "tuneable" then u can click the button tuneables right below. if u do so u got a list of all the tuneables. search for freq limit sleep and give it the Value of 0. save, done
[ONE Android Development] brisac:
What for those who dont have donation package app?
[ONE Android Development] jmtjr278:
Donate or wait for the next version. Sounds like Zane has a plan b if our lord doesn't squash the bug.

Sent from my A0001
[ONE Android Development] andip71:
... Or use another governor for the time being.

... Or try Trickster Mod app (can work, but not sure)

Btw, I cannot squash the bug as it came suddenly without a change. So I expect it to disappear as well silently with next updates ?

Andi
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

uploaded builds for Boeffla-kernel-4.0-beta4-CM12.1-bacon

hopefully without zzmoove issues :)

enjoy!

ZZ
[ONE Android Development] brisac:
tried official boeffla beta4 and didnt get any locks on power button and no issues on zzmoove :D hopefully we won't have any problems anymore. thanks [MENTION=3279788]ZaneZam[/MENTION] once again :D
[ONE Android Development] ZaneZam:
ehm i case someone uses the "u500" build from today, plz re-download/re-flash this build i forgot to remove "plan b" (disable of all freq limits in all profiles)

no big deal but sry ! :o
[ONE Android Development] vurtomatic:
[MENTION=3279788]ZaneZam[/MENTION] Do you have instructions for your Boeffela app?

I accidentally changed the settings in the Default profile and want to revert them back to default. I didn't know I should've created a new profile first and change the settings in that.

[Edit: I found the buried reset, thanks.]
[ONE Android Development] andip71:
And for completeness: Full documentation is available on the kernel homepage.

Www.boeffla-kernel.de

Andi
[ONE Android Development] ZaneZam:
and for correctness : Lord boefflas app :)
[ONE Android Development] smint86:
Downloaded the mentioned build earlier today (about 4 hours before your post) and used it till now, with zzmoove battery yank, native hotplug. No problems so far. Will redownload it again, anyway :).
[ONE Android Development] ZaneZam:
thx, yeah this build was kind of double fixed :) with the new one u can enjoy the freq limit again, so everything is back to normal.
[ONE Android Development] smint86:
Had a random reboot, just while typing, without a freeze before, directly rebooted.

Kernel v4.0 beta4 (second version, u500), ROM Temasek v9.7 (CM12.1).

- CPU: gov zzmoove battery yank, native hotplug

- GPU: gov simple_ondemand

- touch boost at 1267 mhz

- i/o fiops at 1024

- rest stock

Last_kmsg: https://www.dropbox.com/s/keo39qi9z7gz1ul/last_kmsg?dl=0
[ONE Android Development] ZaneZam:
hmm no major crash but plenty of never seen ones before:

------------[ cut here ]------------
[ 5281.147475] WARNING: at kernel/irq/manage.c:428 resume_device_irqs+0x5c/0x94()
[ 5281.147493] Unbalanced enable for IRQ 61
[ 5281.147507] Modules linked in:
[ 5281.147570] [<c0113e68>] (unwind_backtrace+0x0/0xfc) from [<c01c53c8>] (warn_slowpath_fmt+0x6c/0xec)
[ 5281.147619] [<c01c53c8>] (warn_slowpath_fmt+0x6c/0xec) from [<c02652f0>] (resume_device_irqs+0x5c/0x94)
[ 5281.147662] [<c02652f0>] (resume_device_irqs+0x5c/0x94) from [<c05b8840>] (dpm_resume_start+0x10/0x24)
[ 5281.147705] [<c05b8840>] (dpm_resume_start+0x10/0x24) from [<c0221e14>] (suspend_devices_and_enter+0x29c/0x400)
[ 5281.147745] [<c0221e14>] (suspend_devices_and_enter+0x29c/0x400) from [<c0222240>] (pm_suspend+0x2c8/0x33c)
[ 5281.147781] [<c0222240>] (pm_suspend+0x2c8/0x33c) from [<c0220f68>] (state_store+0xd8/0x174)
[ 5281.147827] [<c0220f68>] (state_store+0xd8/0x174) from [<c03866fc>] (sysfs_write_file+0xe4/0x1a8)
[ 5281.147882] [<c03866fc>] (sysfs_write_file+0xe4/0x1a8) from [<c0304ca4>] (sys_write+0x100/0x264)
[ 5281.147935] [<c0304ca4>] (sys_write+0x100/0x264) from [<c010c45c>] (__sys_trace_return+0x0/0x24)
[ 5281.147957] ---[ end trace c8acf753d965b1b3 ]---

can't say where the problem comes from atm
[ONE Android Development] Criton30:
which kernel can I use with stock CM12S without problem?
[ONE Android Development] ZaneZam:
only original for cm12s atm. just came home from work and I have to prepare things ;)
[ONE Android Development] ZaneZam:
New Builds!

now u can download Linaro/Uber builds of Boeffla-kernel-3.0-beta1-CM12s-bacon from HERE or HERE btw. build with updated Uber toolchains from 13.04.15

enjoy!

ZZ
[ONE Android Development] suaverc118:
Just flash U500 for cm12S and had immediate calendar and messenging closing so bad that I couldn't get to apps to clear data, so I flashed U493 with same issue, but not as bad. Was able to clear data and all is well. Didn't have that issue initially with lords original kernel, just these 2. I know its beta, just reporting.
[ONE Android Development] ZaneZam:
OK thx good to hear that u got it in control. well i faced a couple of issues too today after dirty flashing (mainly root problems) but after fixing them everything was back to normal (afaics) and after that all builds passed the quick test, can't confirm any build related issues atm. Maybe a Selinux hiccup? :) kernel is not yet 100% fit for the new rom, but soon will be as lord boeffla stated. so let's see how beta 2 works then.
[ONE Android Development] ravvio:
I m going to flash the test build 3.2 4-09 for CM12. Any suggestions? I an Slimuber latest build.
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

uploaded new builds for Boeffla-kernel-3.0-beta2-CM12s-bacon compiled

with updated Uber toolchains as of 13.04.15 and one NEW build with UBERTC gcc version 6.0.0 20150413 (experimental)

(can't say anything about this new u600 build yet, it runs since about 30 mins only here, first impression: feels like u500 for now...but let's see ;) )

cheers & enjoy!

ZZ
[ONE Android Development] suaverc118:
Am I blind?? I don't see a link for 12S zips.
[ONE Android Development] S1ay3r666:
here you go!
[ONE Android Development] ZaneZam:
nope i again forgot to edit OP, sry links available now! :angel:
[ONE Android Development] DrNinjaa:
The Lord has baked new Cakes... [MENTION=3279788]ZaneZam[/MENTION] .... We wait for the Ice cream topping which u add every time to make them Yummy ;)
[ONE Android Development] beany>:
And the cherry on top.
[ONE Android Development] suaverc118:
Your u600 is amazing!
[ONE Android Development] ZaneZam:
somehow i'm hungry now :)

next builds might take a bit guys, due to latest changes from the lord i've to manual rebase things and also add the uber 6.0.0 variant, but im on it so stay tuned... ;)
[ONE Android Development] Fenvarien:
Take your time, your work and support here is highly appreciated! :good: :)
[ONE Android Development] ssbnasa:
Just a small query.

I'm using Blisspop 5.0.2 rom, so i have to flash Cm12 official/nightlies zip, right?

Thanks!
[ONE Android Development] cerealguy:
Yessss! :)
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

ok here we go with the new ones:

Boeffla-kernel-4.0-beta5-CM12.1-bacon

Boeffla-kernel-3.2-CM12-bacon

Boeffla-kernel-2.6-CM11-bacon

Boeffla-kernel-2.6-CM11s-bacon

builds uploaded!

+added uber 6.0.0 CM12x builds (building of CM11x versions not tested but most likely they won't boot like uber 5.0.0 builds)

enjoy

ZZ
[ONE Android Development] vurtomatic:
Been using u500. Is u600 the new recommendation? Spoilt for choices now :confused:
[ONE Android Development] ZaneZam:
as it works really great (at least as good as u500) i would say yes. yeah there are many versions around atm, and thats mainly to give u options ;) might be that i drop some in the near future (also because of lesser workload) but in general, i use to use always the newest/latest toolchain version till any problems appear which might be related (well thats difficult to say actually), then i try the others.

but i must say i never had to do this, everything was fine with u500 and is fine now with u600 ;)
[ONE Android Development] Mrwargod:
I've been using the u600 version of the 3.2 stable since yesterday. So far is running great. :good:

Can't really say i've noticed an improvment over u500 but since i also like beeing on the latest version possible and i havn't met any problem yet i'll stick with this one.
[ONE Android Development] gondsman:
Code for gcc 6.0 was just branched, so I assume it's still almost the same at this point...
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

and here we go with the next one:

builds for new version Boeffla-kernel-4.0-beta6-CM12.1-bacon uploaded!

enjoy!

ZZ
[ONE Android Development] ZaneZam:
yes no additions needed, just one file to be able to build with gcc 6.0, thats it ;)
[ONE Android Development] ZaneZam:
New ones!

Hi Guys,

builds for :

Boeffla-kernel-4.0-beta7-CM12.1-bacon

Boeffla-kernel-3.3-beta1-CM12-bacon

Boeffla-kernel-3.0-beta3-CM12s-bacon

Boeffla-kernel-2.7-beta1-CM11-bacon

Boeffla-kernel-2.7-beta1-CM11s-bacon

just uploaded!

enjoy!

ZZ
[ONE Android Development] ravvio:
What's the difference between 12 & 12s kernel builds. I am on SlimSaber Rom (Uber build) which should I use. Little Confused. :confused:
[ONE Android Development] Mrwargod:
Use the CM12 version - 3.3 beta 1
[ONE Android Development] ZaneZam:
cm12 is for official CyanogenMod roms and cm12s for new CyanogenOs stock Opo. and yes it's getting confusing :)