yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] lou2s:
I too feel the battery is dropping faster than usual after flashing the kernel with new touch driver. But today is sunday so it's hard to tell. Will test overnight drain and normal usage tmr on monday.

I read from some thread that with new touch driver when u touch the cpu will be at max freq with 2 cores on. Dunno if this is causing the extra battery drain.

Definitely feel a bit better in touching experience, though I never had serious screen problem except when I was using the phone on the beach.

Sent from my Boeffla-ised Euphoria 1.1 A0001
[ONE Android Development] davebugyi:
People are reporting higher battery drain when idle with the new drivers across multiple threads unfortunately.
[ONE Android Development] brisac:
Well good to know. Thanks. Hopefully this will be fixed soon..
[ONE Android Development] andip71:
I also feel the new drivers are a bit more energy hungry.

So seems, everything comes with a price...

Andi
[ONE Android Development] Fenvarien:
I'm not sure about the source of the drain. With WiFi off I had no unusual drain over night. Probably the new WiFi drivers are the problem? Or the touch firmware drains only with the screen active and/or DT2W enabled, which is switched off on my OPO (I'm using the swipe features of Boeffla-Kernel).
[ONE Android Development] andip71:
But the WiFi drivers are in for almost a week already, this is therefore not likely...

Andi
[ONE Android Development] joefso:
[MENTION=3279788]ZaneZam[/MENTION]

could you also build the beta14 build?
[ONE Android Development] lou2s:
Since the drain is quite a lot, I just went back to beta13... (6.5hr sot vs 4hr...) and I didn't really hv touch problem, so far...

Sent from my Boeffla-ised Euphoria 1.1 A0001
[ONE Android Development] suaverc118:
I'm on the latest build of bliss and flashed back to beta 14. We will see how this works. I feel a little difference in typing but nothing a little tweaking of the kernel settings can't fix.
[ONE Android Development] davebugyi:
After a little fiddling around, beta 14 (no new touch drivers) seems to drain less. As for the touch part. I did not have issues before, so did not notice anything strange.
[ONE Android Development] joefso:
where is 2..7 ? it does not seem to be available in the archives?
[ONE Android Development] ZaneZam:
sry, but there was never a 2.7 build, i only did 2.8 ;)
[ONE Android Development] joefso:
alright, thanks for providing these builds anyway
[ONE Android Development] brisac:
[MENTION=3279788]ZaneZam[/MENTION] any possible "fix" for battery drain caused by new touch drivers?
[ONE Android Development] ZaneZam:
nope not aware of any fix, I even don't know if I have it. I was/am busy with zzmoove 1.0b7. facing again a "hard nut" so no eyes for anything else ;)
[ONE Android Development] Fenvarien:
Disabling DT2W and proximity check seems to stop or mittigate the battery drain.
[ONE Android Development] brisac:
U tryed that?
[ONE Android Development] suaverc118:
How do you do proximity check?
[ONE Android Development] Fenvarien:
Yes, since several hours. It's working great for me. Other guys in the general CM 12.1 thread tested it too.

As it seems the new firmware is going to be reverted quite soon until they find a new fix. http://xdaforums.com/showthread.php?p=60802745

http://review.cyanogenmod.org/#/c/98677/
[ONE Android Development] brisac:
Ummmm just got this message when opening an app. Do i need to activate mpdecisio in kernel auditor?
[ONE Android Development] Fenvarien:
Do you use kernel adiutor and Boeffla config? I would not recommend to use more than one kernel tool. Besides that I remember to have read something about this issue in the kernel's main thread some weeks ago. This user had ak kernel installed prior to Boeffla-Kernel.

/edit: Here is the link: http://xdaforums.com/showthread.php?p=60384801
[ONE Android Development] davebugyi:
I agree. I know from personal experience that havin multiple kernel tuning apps can generate a lot of issues.
[ONE Android Development] brisac:
Kernel auditor is built in rom... Never had and issue with it, but now i got this message
[ONE Android Development] tobitege:
Just as an FYI: CM did revert last night the Synaptics (touch panel) commit for the OnePlus kernel, so next build by Andy will surely have it ready.

http://review.cyanogenmod.org/98677
[ONE Android Development] ZaneZam:
indeed, he's already working on it, but this time its a bit more work for him due to many CM12.1 commits conflicting with upstream. i hope i don't have to do TC fixes again. if so it will also take a bit longer to bring out my builds. but let's see :fingers-crossed:
[ONE Android Development] beany>:
Or get rid of Kernel Adiuter using Titanium Backup - that's what I do. Or you could include it in a de-bloat script.

I believe this is referring to disable accidental wake up.
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

Boeffla-kernel-2.9-CM11-bacon

Boeffla-kernel-2.9-CM11s-bacon

Boeffla-kernel-3.5-CM12-bacon

Boeffla-kernel-3.0-beta8-CM12s-bacon

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

Boeffla-kernel-3.0-beta4-OOS12-bacon

builds uploaded!

Enjoy!

ZZ
[ONE Android Development] mammenj:
Version 16 for CM 12.1 will work with only new build (ramdisk)?
[ONE Android Development] dickenam:
ROM or NIGHTLY built on or after 14.05 [emoji106]
[ONE Android Development] mammenj:
You meant ROM built after 14.05? Right?
[ONE Android Development] OmegaBlaze:
I get this same thing in uber cm12.1(5/14)

Im about to go back to 5/18 build.. Shlt works fine. No errors.
[ONE Android Development] dickenam:
Yep, sry.
[ONE Android Development] Ahmed Shawky:
need some help

Guys,

Just small question can not find the answer of here

I use Bliss POP ROM 5.1.1 and Have major Touchscreen Issue

1- Does this Kernel will make the touchscreen work flawlessly ?

2- Can I flash it with bliss pop rom or only work with CM12 ?

3- is there any battery drain ?

4- what is the other benefit from flashing this kernel ?

5- which ver should I use specifically that work with me case with zero error ?

Thanks in advance
[ONE Android Development] abhibnl:
1. Not the latest one. Use the version with the new touchscreen firmware. I guess it was beta 15.

2. Boeffla kernel has different versions for cm12 and cm12.1. So choose accordingly.

3. It's highly subjective. But battery drain on new touchscreen firmware + dt2w has been found.

4. It won't do any magic. It's a kernel based on stock with complete control over how you want it to perform.

5. The version that is meant for the base of your rom.

Now again, every single question might have been answered in the thread already.

Sent from OnePlus One
[ONE Android Development] Ahmed Shawky:
Thanks very much

but about my question that i flash now Bliss pop rom NOT CM rom 12 or even 12.1

so can i use it ??

and beta 14 is more much smother ?
[ONE Android Development] Ahmed Shawky:
Thanks , but what do you mean but touchscreen firmware update ?

I will flash this over Bliss pop is that ok ?

---------- Post added at 02:53 PM ---------- Previous post was at 02:48 PM ----------

just another question please

if I flash this to solve the touchscreen issue and facing very bad drain issue

how can back again to the stock Kernel ? I use Bliss POP v 3.3
[ONE Android Development] dickenam:
To get to stock kernel, you will re-flash (read: dirty flash) your ROM
[ONE Android Development] Ahmed Shawky:
Thanks

but if dirty flash will not be stable like clean flash I`m right ?
[ONE Android Development] ZaneZam:
New versions!

of course :)

yeah thx to u [MENTION=2875820]f100cleveland[/MENTION] :)

and here we go :

just uploaded new images for

Boeffla-kernel-2.0-beta7-CMs-bacon

Boeffla-kernel-2.0-beta7-CM-bacon

Boeffla-kernel-2.0-beta7a-CM-bacon

..aaand i want to let u know that i switched from -O3 optimization to -Ofast in linaro builds (sabermod not possible due to a toolchain crash when building with -Ofast)

let's see how they play now.. my first impression was a minimal increase in snappiness but well form your own opinon by using it ;)

Enjoy!

ZZ
[ONE Android Development] cerealguy:
Guys, I've used always original version of Boeffla... Which of this modified version do you suggest to try? Linaro or Sabermod? :)
[ONE Android Development] ZaneZam:
try them both and compare, as always at the end it depends on your experience with the corresponding build

but atm i would suggest linaro build . ;)
[ONE Android Development] cerealguy:
Thanks man! I've flashed linaro build on latest CM remix Rom and I can feel the difference compared to Boeffla stock version! :D
[ONE Android Development] hcgl:
After flashing cm 11 sabbermodded beta 7a my WiFi doesn't work :'(
[ONE Android Development] ZaneZam:
u know about that? : http://xdaforums.com/showpost.php?p=56423899&postcount=640

u have to be on latest nightly 01.11.2014 if u use beta7a
[ONE Android Development] hcgl:
Oh okay - i didn't see that.. Thanks for your work by the way! ;)
[ONE Android Development] beaverhead:
works great with latest temasek.great work man.
[ONE Android Development] otisman:
All is well perfect match w03slimkat and boeffla kernel much alohas
[ONE Android Development] otisman:
Sick batt life on beta 7 w03slimkat unreal
[ONE Android Development] emam damon:
hey guys.sorry i'm kind of new here. i came from nexus 5 which has excellent kernels like elemntalx in terms of smoothness.

i was searching opo thread to find such a kernel until i found this kernel and it is awesome in terms of general and app scrolling smoothness

but i have had huge battery drain. i'm using linaro version with zzmoove and row.i lost 10 percent in 30 min SOT.

what can i do about that?
[ONE Android Development] DerRomtester:
This is quite normal for me 10*30=300min = 5hours SOT
[ONE Android Development] andip71:
I think it depends very much on what is done during the time.

If playing games or surfing the net via 3G/LTE, it is kinda normal.

In wifi, just doing usual stuff like reading mails etc, I gain much more and I lose approx. 1% every 6-7 minutes only.

Andi
[ONE Android Development] Setting.Out:
I had Asylum LS installed with this kernel and had it drop 30% in two hours, and with the same setup with Carbon it literally went for days.. There are more factors than just roms/kernels.. Wakelocks, usage, signal, temperature... The list will keep going will greatly effect battery life. Also keep in mind your phone rarely tells the truth about how "fully" charged it is.. Often times a 100% charge is more like 90%, so it'll look dramatic, but the phone is just catching up to reality...
[ONE Android Development] emam damon:
5 hour SOT is also normal on nexus 5 with elementalx kernel.i thought opo battery is batter than that.

i was on wifi doing normal staff like g+,gmail,...

and yes i have exact same of app like my nexus 5.
[ONE Android Development] Aavion:
unpatiently waiting for the Ofast linaro build of beta 8 :o
[ONE Android Development] ZaneZam:
2.0 beta 8 builds uploaded!

available NOW! :D

enjoy!
[ONE Android Development] Aavion:
thank you very much! [emoji4]

much faster and snappier than expected!

for those who care: hit 47860pts in antutu without oc using zzmove gov :) pretty nice! i thought those results are only reachable using Performance gov?!
[ONE Android Development] Shaddy-Z.:
Does zzmoove still cause music to sometimes become static-e or mess up? I know that you implemented some instability fixes to that governor in the recent beta and was wondering. I know that increasing the screen off clock is a current fix but just curious. However I'm still getting such great battery life on slim+row with awesome performance on original Boeffla. Gonna give the linaro build a try since you recommended it!

Trying zzmoove+optimal/fiops atm :)
[ONE Android Development] suaverc118:
What is oFast?
[ONE Android Development] dickenam:
It won't be any less stable, per se. You're just flashing what you're already running over top of itself. If it were a different ROM, that would be a different scenario.

:thumb up:
[ONE Android Development] Ofthecats:
Oos12 u600 does not boot for me at all. Goes black after "1+ powered by Android "
[ONE Android Development] Ahmed Shawky:
Thanks

can you give my any guid for dirty flash
[ONE Android Development] dickenam:
Same as clean flash, just don't wipe beforehand.
[ONE Android Development] ZaneZam:
Hmm for me it does boot .Bad download or flash? Other builds are booting?
[ONE Android Development] Ofthecats:
I'm back on beta5 stock for now. I will try when you manage to update builds
[ONE Android Development] ZaneZam:
New Builds!

now u can try the new ones as ive just uploaded builds of

Boeffla-kernel-3.0-beta5-OOS12-bacon

;)

enjoy!

ZZ
[ONE Android Development] Rainbowtoast:
Is there a mirror for the beta15 build? I'd like to test the touch firmware but missed that build (I have beta14 and am currently using beta16). I looked in the outdated builds but couldn't find it.
[ONE Android Development] abhibnl:
Out of curiosity, how long have you been flashing roms?

Sent from OnePlus One
[ONE Android Development] Ofthecats:
None work except stock boeffla.

Strange.
[ONE Android Development] ZaneZam:
yeah really strange, no clue why it should not work for u. anyone else with problems?
[ONE Android Development] evertking:
hate to say it but me too

Same problem here. Used this kernel for awhil3 but soon as the switch it stopped working.
[ONE Android Development] ZaneZam:
sry for my dumpishness but what is awhil3 ?? :)

if it is a rom then all i can say is all builds are working for me on OOS 1.0

stock

;)
[ONE Android Development] _Man0waR_:
I think he meant 'a while'
[ONE Android Development] ZaneZam:
lol yes makes sense,I guess I've to update my leetspeak knowledge :)
[ONE Android Development] evertking:
Which version should be flashed with slimsaber 5.1? 12.1 right? Bit get stuck at boot logo for awhil3
[ONE Android Development] merikgvr4:
Boeffla kernel 4 beta 16 won't boot with latest slimsaber. Please help.
[ONE Android Development] 1ceb0x:
I have created, what i believe to be a speedy, buttery smooth experience profile, but with a drive for battery, with conservative + zen at 2048 read ahead, cpu max at 2.2, -50 uV, gpu simple ondemand, optimized hotplug and Speemod tweaks.

for who is interested, download from here (boeffla config app is needed): https://copy.com/b3EhoNiTZLHqK3Wq

all this with latest resurrection remix rom.

peace!
[ONE Android Development] hassan_1000:
Probably tried all the opo kernels but always come back to uber boeffla
[ONE Android Development] suaverc118:
After downloading how do we install or open? Thanks.
[ONE Android Development] mp3deviant721:
Copy to "boeffla-kernel-data" folder and go into the Boeffla app and load the profile from the "Profile maintenance" page.

OnePlus One | Powered by Temasek x Boeffla
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

i've just uploaded builds of:

Boeffla-kernel-3.0-beta9-CM12s-bacon

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

and

Boeffla-kernel-3.0-beta7-OOS12-bacon (this one has a little changelog : fixed kernel string to show correct upstream version, images compressed with gz again instead of lzma -> might fix no-booting issues!)

before someone asks: i will maybe do the special touch driver version which lord boeffla provides in addition when i have time, but not in the next two days ;)

enjoy!

ZZ

PS: mediafire pending...
[ONE Android Development] idprophecy:
Thanks a lot for uber version ... By the way is kernel compiled with the latest toolchain ? Boeffla Config doesn't show version of toolchain I don't know why, I am on u511, thanks. :)
[ONE Android Development] davebugyi:
Is the latest 4.0-beta17-CM12.1-bacon has the "new battery drainer" patches in or is the one without? Just asking, because there are 2 versions now. :)
[ONE Android Development] dickenam:
He mentioned no in his post. Maybe, in a few days :confused:
[ONE Android Development] davebugyi:
I am BLIND :silly: No, that is OK, because I do not want a kernel with those drivers.
[ONE Android Development] Ofthecats:
Oos12-beta7 u600 booted!
[ONE Android Development] ZaneZam:
nope its compiled with uber version from 01.05.15 as i missed the last update :o

you don't see that in boeffla config? nevers had that, what about other tools like cpu spy for example, is it shown there?
[ONE Android Development] idprophecy:
I tried many tools, but it doesn't show the date of the update of tc, just if it is u511, u493 or u600. It probably happens only on the u511, coz it appears on u600 ... I haven't tried u493. Nevermind, it isn't important. :)
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

i had a bit time earlier than expected so u can also download now builds of:

v3.0-beta9-CM12s-bacon-touch-workaround

v4.0-beta17-CM12.1-bacon-touch-workaround

v3.0-beta7-OOS12-bacon-touch-workaround

enjoy!

ZZ
[ONE Android Development] 1ceb0x:
Hello,

Just wanted to report that v4 beta16 and beta17 (linaro and uber) for CM12.1, are not booting on SlimSaber build 25 May 5.1.1.

Cannot take a logcat, unfortunately. Is anyone else able to boot the kernel on SlimSaber 5.1.1?

another user with the same problem PMed me (he has the same issue on both Slimsaber and SlimLP): [MENTION=6685094]cyx2626[/MENTION]

[MENTION=3279788]ZaneZam[/MENTION] do you use anykernel method?
[ONE Android Development] suaverc118:
With the new work around, do we need to install the touch zip or is this automatic just flashing the kernel?
[ONE Android Development] ZaneZam:
sry I dunno why it doesn't boot on that versions, would have to check. may I ask if it does boot with original boeffla kernel?

and nope it's a pure boeffla so no anykernel method ;)

nope just flash ;)
[ONE Android Development] 1ceb0x:
nope.. doesn't want to boot on slimsaber using stock boeffla or your versions... [MENTION=1228651]fusionjack[/MENTION] [MENTION=3306843]kantjer[/MENTION] - Boeffla kernel is not booting on SlimSaber (one user said SlimLP as well but I haven't tested that version).. I currently cannot provide a logcat because I'm not near a computer but I'll try to provide one asap. if you guys have some time to investigate, that would benefit a few other users who love boeffla and Slim (although i know you guys will always recommend the stock kernel).. cheers!

[MENTION=3279788]ZaneZam[/MENTION], sorry for highjacking your thread with this.
[ONE Android Development] ZaneZam:
no problem buddy no "hijacked" feeling here :) but yes in that case it's (again) a general problem with compatibility. right our reference is always a stock rom. with none stock roms there is everything possible. ;)

you can provide a log (if u can, which i strongly doubt in that early stage)

but time is always limited and full of other stuff as u probably know.

I would guess it's the ramdisk and as u already mentioned maybe the any kernel method can fix that but well someone would have to do that as the Lord and I will not, sry. I'm not that much into that any kernel thing here on opo but for i9300 devices it was just a matter of "extracting", exchanging ramdisk, editing scripts and repacking stuff again. dunno if that also applies here too.
[ONE Android Development] brisac:
These have included new touch drivers or not?
[ONE Android Development] Fenvarien:
Yes, they have the new but battery draining touch firmware.
[ONE Android Development] joefso:
why are the linaro builds so large in size compared to the others? ( cm12.1 )

Yes, I tested regular boeffla on slimlp 5.1. Does not boot unfortunally.
[ONE Android Development] ZaneZam:
because other toolchains and the used optimized compiler flags like -Ofast are generating more code

hence bigger images. usually i try to react such things by using other compression methods like lzma, which

can shrink the size to a "normal" level again, but that compression method doesn't work well on opo sources

(see OOS builds, don't boot problem) so i leave it to stock gz compression now. but that size topic applies only to

the OOS builds as with the others lzma didn't even work out of the box, so never used other compressions than gz for

the others.

ok thx for the info then we have slimlp also on the "not compatible" list. :(
[ONE Android Development] andip71:
Yep, just to add on some details on that:

Meanwhile Slim is not compatible with CM anymore.

This is mainly due to one difference in the ramdisk: init.environ.rc, here specifically the setting SYSTEMSERVERCLASSPATH.

Slim has a different one, that is why it does not boot up anymore.

Second, slim does not support mpdecision out of the box (although it is contained in disabled state in the rom).

This would mean:

In order to make my kernel to work on Slim, I would need to provide a complete separate variant. Technically not a problem, I have a test kernel running just for proof-of-concept. But I will not add another variant to my list of official kernels, cannot handle more atm.

Andi
[ONE Android Development] Mrwargod:
Thank you for your explanation.

So, if i could manage to learn how to build a kernel from source, it would be possible for me to build your updated versions with that modification?
[ONE Android Development] andip71:
Yes sure, of course.

Andi
[ONE Android Development] Mrwargod:
Nice. :)

I guess i just got a new aim then. Compiling a kernel doesn't seem as plain as compiling a ROM, but i'm gonna start looking into it. :good:

Thanks.
[ONE Android Development] ZaneZam:
a good starting point would be to use the great bbuild. sh script Lord boeffla provides in all his repos now. if u manage to build one working pure original image then u can start messing around with the needed changes. just a little hint ;)
[ONE Android Development] Mrwargod:
Thanks for the tip. :)

Downloading the repo and starting to try and figure it all out now.
[ONE Android Development] abhibnl:
Btw, what's the total size of the repo? Is it also like 10-20gb in case of roms or is it less in size?

Sent from OnePlus One
[ONE Android Development] Mrwargod:
Around 150 Mb.
[ONE Android Development] abhibnl:
That's really fine! I'll Pm you for further inforation while i'm home to learn about how to build a kernel from source. I hope you would have no issues with an apprentice, would you? :P I wanted to learn how to build roms from source but due to my internet connection speed in India, 20GB of data will take atleast 7-10 days to download.
[ONE Android Development] ZaneZam:
New Builds!

Hi Guys,

the new builds of versions:

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

Boeffla-kernel-3.0-beta10-CM12s-bacon

Boeffla-kernel-2.10-beta1-CM11s-bacon

Boeffla-kernel-3.0-beta8-OOS12-bacon

are available now... :good:

have fun!

ZZ
[ONE Android Development] andrea90:
Boeffla-kernel-3.0-beta10-CM12s-bacon with linaro is just perfect, never used such a smooth phone not even an iPhone...
[ONE Android Development] mammenj:
Will 13zz work on slim saber? Or which version has the older ramdisk compatible with slim saber?
[ONE Android Development] ZaneZam:
New Builds!

sry i don't know, maybe someone else can give u that info, ooor make a backup (anyway mandatory *g*) and check yourself which one runs.

so guys here the rest of the OPO builds:

Boeffla-kernel-2.10-beta1-CM11-bacon

Boeffla-kernel-3.6-beta1-CM12-bacon

uploaded...

enjoy!

ZZ
[ONE Android Development] kaibosh99:
I must be out of the loop, it seems that some roms have fallen out of compatibility with this kernel due to ramdisk issues? I had a look, I couldn't see any list in the OP or anywhere else that shows which roms can or cannot be used anymore. Can anyone tell me if the newest Euphoria (as of 6/02) is compatible with the uber 600 CM12.1 release?

edit: Tried it myself, working perfectly with no issues.
[ONE Android Development] brisac:
No updates with new touch drivers or they are in?
[ONE Android Development] davebugyi:
They are included.
[ONE Android Development] brisac:
aham, new unofficial like lord boeffla said?
[ONE Android Development] ZaneZam:
Yes but meanwhile they are official ;)
[ONE Android Development] CounterC:
Sorry to jump in here guys but I just did a clean flash with Euphoria (02/06). How to install latest Boeffla by Zz? Thanks in advance...
[ONE Android Development] tobitege:
Download the correct CM 12.1 version from first post and flash the zip like any other kernel.