yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] chiujiewei:
[MENTION=947981]Lord Boeffla[/MENTION]

multiboot is working great..on he latest cm12s kernel..i dont know why soe people report it to be not working..guess they didnt inject the boot sector after flashing the kernel :)
[ONE Original Android Development] magnamentis:
thanks, best possible solution as always :)

---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ----------

it can depend on which rom your run as primary and which as secondary and similar. it works however so it must be a user error.
[ONE Original Android Development] Orphee:
Multi boot is working great with cm12s as primary. No issue at all.
[ONE Original Android Development] molonad:
Hi again mistr lord boeffla :D please i have little issue with every zzmove governor , i love speed of governor and native horplug but i hate that little delay when is phone long time sleeping , with default hotplug or optimized and interactive and others is delay minimal . for example sometimes when someone call me is screen black 2 , 3 seconds , can i somelike in tunables reject this delay ? i understand that phone has a good sleep with it , but for me is zzmove optimal best and only thing i hate about it is only this delay :) for example in battery zzmove profiles i dont care about this delayed wake :) thanx for help
[ONE Original Android Development] fmc000:
Maybe because not all of us have touchscreen problems but have the battery drain?

---------- Post added at 07:57 PM ---------- Previous post was at 07:56 PM ----------

Exactly.
[ONE Original Android Development] magnamentis:
you're all correct from your perspective, that's why he let's us choose :)

BTW it seems like they simply addressed the wrong core. 1%/h is what i get on my nexus 5 which does not have the low power core. solution is to make switch deactivate and activate dt2w via tasker script on charger / off charger and/or with the power button, while the latter makes only sense if we have it on charger on the desk at work or so which i do. the power button off is a feature which for example was added by [MENTION=4684315]flar2[/MENTION] as a tunable in his app.
[ONE Original Android Development] andip71:
This can only be addressed by Mr ZaneZam, the developer of zzmoove.

I am not putting messy code into his governor [emoji6]

But I think, if this is a real issue for you, zzmoove might not be the perfect governor for you.

Andi
[ONE Original Android Development] denyo81:
First release (beta2) and second release (beta3) of the new Synaptics driver works perfect in Kernel. But now I'm faced a little different of the first release's and bring back the delay touches/non touches. I really believe the touchscreen issues is a hardware problem. But the new Synaptics driver shows me a other picture. Hope this would be better in next updates. My Opo makes me crazy ?
[ONE Original Android Development] Mrj0to:
[MENTION=947981]Lord Boeffla[/MENTION] Does the 12.1 kernel work on 5.1.1? Thanks!
[ONE Original Android Development] suaverc118:
I feel stupid for asking this and please forgive me. I did like the responsiveness of the touchscreen zip that was put out. Since then I've flashed the latest bliss with Zanezam U600 beta 15 kernel. I have not flashed that zip since the last build. Am I just on regular set up or do I have to flash the zip to get the responsiveness back? And if so, do I have to stay on beta15 to keep that? Does flashing beta 16 change anything with that zip? Thanks.
[ONE Original Android Development] gazou_hb:
Yes. boeffla-kernel-4.0-alpha4-CM12.1-NG-i9300.recovery.zip

Envoyé de mon GT-I9300 avec XDA Forums PRO
[ONE Original Android Development] denyo81:
[MENTION=947981]Lord Boeffla[/MENTION], please put my post in oxygen kernel thread. Thanks
[ONE Original Android Development] andip71:
Only a mod can move posts, I cannot.

But not a problem, the post is also not wrong here :)

Andi
[ONE Original Android Development] Lakino:
The touch screen issue affects only certain units of the 1+1. Many of us are not affected - - me included - - and we certainly don't want to take this significant battery life hit with this new driver.

It's nice to have two versions I suppose for those that are severely affected by the touch screen issue.
[ONE Original Android Development] nicolahaye:
Just wanna say thanks again for your kernel. Combined with euphoria 1.1 today is the first time I've reached 7h30 SOT !! And I still have 14% left xD
[ONE Original Android Development] mucinch:
[MENTION=1045701]lordbo[/MENTION]effla I am Wifi disconnect on sleep problem with 4.0 Beta 16 on cm12.1 0518 nightly, but it works fine with beta 15.
[ONE Original Android Development] andip71:
Thanks, but what do you want me to do?

I am very happy with the latest wifi drivers CM put into CM12.1. So will not revert them out. Especially as nobody else mentioned any wifi issue.

I just use official code for wifi, nothing tweaked. So it is noted for awareness.

Andi
[ONE Original Android Development] mucinch:
No problem, Thanks.:)
[ONE Original Android Development] Emway:
Just curious... Which kernel version nicolahaye?
[ONE Original Android Development] nicolahaye:
I'm on euphoria from may 3rd so I used the beta 13 if i'm not mistaken. I use zzmove optimal. But to be honest, I got 7h30 with only browsing, reading and casting music to my Chromecast. Always on WiFi, no 3/4g :) and I didn't play any heavy games either.

But still it rocks :)
[ONE Original Android Development] DjDiabolik:
Little ot about my previous question about my issues on boot fail :

Apparently i don't have no more problems....

Thanks otherwise to [MENTION=947981]Lord Boeffla[/MENTION] and other members have tryed to suggest me some solution.. this problems it's disappeared like if appeared mysteriously ;)
[ONE Original Android Development] Bloodykiller86:
Man that beta15 has saved my phone. This touchscreen lag and non responsiveness was driving me crazy and finally it works like it's supposed to. Luckily idc about dt2w so i have that off. Battery seems fine to me. Just glad to actually be able to move things. Texting was a nightmare and scrolling through things was painfully slow so thanks. Hopefully they fix the battery drain later on but til then im sticking to beta15
[ONE Original Android Development] alexbk66:
Logcat error

I found the following error (many of them) in logcat:

Googling for this error indicates that other kernels have it too. Is it something to worry about?
[ONE Original Android Development] andip71:
I am not worried, no.

Sometimes errors are informational and to be accepted.

Andi
[ONE Original Android Development] SLBoy:
Just a quick question, why doesnt beta 16 work on euphoria?
[ONE Original Android Development] cr0wnest:
Flashed the CM12 version 3.5 and my wifi is really spotty now. It either takes forever to connect, or does not connect at all, or shows that its connected but doesnt work. Running on Exodus ROM. Is this a known issue with the kernel?
[ONE Original Android Development] magnamentis:
because euphoria most probably needs to be updated to cm12.1 15th of may or younger.
[ONE Original Android Development] andip71:
It is not a known issue with the kernel.

It might be more an issue with your wifi network.

Network working flawlessly here.

But you can always go back to previous kernel version (3.4 in your case) and see if it is better then.

Andi
[ONE Original Android Development] alexbk66:
Isn't Exodus 5.0.2?
[ONE Original Android Development] xflowy:
could you tell me which previous version i need to install to have the touchscreen fix?
[ONE Original Android Development] Mentalmuso:
Beta 15 for cm12.1

---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------

Reboot router?
[ONE Original Android Development] ricardowec:
Lord : I am on latest BlissPop with your Beta 16.

Doing fine except for the annoying WiFi issue.

It has been suggested that latest Metllized Kernel fixes the problem.

Could you take a look and see if something can be done in your kernel in order to help your loyal fans :)

Thanks
[ONE Original Android Development] andip71:
Well, two things again:

a) I have no issues with wifi

b) I am following 100% CM12.1 wifi driver code. When they find it is bad, they will revert it

So, I have no plans to experiment with it currently. It seems for the majority, wifi is not an issue - which leads me to the conclusion it has to do with certain wifi configurations/routers only.

Andi
[ONE Original Android Development] lou2s:
There is definitely problem with lollipop wifi. WIFI works fine with my home and office network, but for a restaurant that I usually go to, I cant connect anymore after moving from cm11s to cm12s. Not only on Oneplus one, my wife's htc one had similar problem (stock rom no root). When we were on holiday, her lollipop htc one couldnt connect to the hotel wifi, while her father kitkat can.

Sent from my AK-Skulled Euphoria 1.1 A0001
[ONE Original Android Development] lou2s:
I have flashed this as well, helped with my connection with 6D, but not the restaurant (and ofcoz I wont be able to change their router setting to suit my phone, if any setting helps)

Sent from my AK-Skulled Euphoria 1.1 A0001
[ONE Original Android Development] fmc000:
Any chance you build a kernel based on beta16 but with the new touchscreen firmware?
[ONE Original Android Development] andip71:
Technically yes, time-wise no.

Just use beta15 instead, on own risk (who knows what else was fishy with the new drivers...)

Andi
[ONE Original Android Development] fmc000:
:good:

That's what I'm doing right now but I thought that the 55 kernel commits and the new wifi drivers were worth asking ;). I actually don't have problems with the current touchscreen drivers but the reverted ones give a different feeling, possibly a placebo knowing that other people see a real improvement with them.
[ONE Original Android Development] andip71:
"There is no free luch"... :) (famous saying)

Well, if you have no touchscreen issues I would use beta16 instead, when I were you.

Andi
[ONE Original Android Development] fmc000:
yeah, will probably do that.
[ONE Original Android Development] gershee:
what is this dhcp fix you speak of?! :eek::D:thumbup:
[ONE Original Android Development] Orphee:
Just flashed it ! Great fix... I had to use static ip since Cos12. Now it works again in dhcp !
[ONE Original Android Development] gershee:
link please.

I looked, couldn't find.

sorry to clutter the thread andy..
[ONE Original Android Development] Galactus:
Is there a thread where people share profiles? Not sure where to start in terms of optimising for a bit more battery life without sacrificing performance much
[ONE Original Android Development] lippol94:
I found myself in a very good spot with Zzmove governor and Yank Battery Governor profile.
[ONE Original Android Development] Galactus:
Cheers, I'll give it a go
[ONE Original Android Development] andip71:
Of course.

Search will give you that result:

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

Andi
[ONE Original Android Development] ethanon:
[MENTION=1470009]boeff[/MENTION]la what kernel settings do you use as a daily driver? Or else what it's the most balanced settings for your kernel. Please suggest.

Thanks
[ONE Original Android Development] dickenam:
Hi Andi,

*bs* I generally use BFQ and I was poking around and found this: http://algo.ing.unimo.it/people/paolo/disk_sched/sources.php

I was just wondering what version you have implemented currently? And if you'd be interested in patching, if necessary. Thanks, per usual!
[ONE Original Android Development] andip71:
I am currently on nightmare governor with tripndroid scheduler. Max CPU freq reduced to 1954 MHz, touchboost also reduced by 200 Mhz.

Rest is pretty much standard settings of the kernel. NO uv and NO oc.

I have v7r5 implemented at the moment, last version is v7r7.

So will plan for an update in the one of the next regular kernel updates.

Thanks for the heads up.

Andi
[ONE Original Android Development] lchiocca:
I've looked into the source code diff for the dhcp issue between aosp and cm. The main ting that changed was the location of the duid file that is being generated (see cm commit 10cb9e2aee0739415d9862a05acc9743528f67e4). The commit comment was:

This seems to be the root commit that is causing the issue. I am a developer, but not a good android/linux one, so I'm asking if someone might know what could potentially go wrong when changing the path the of duid file. For example, would the se policy need to be added/changed for this to work? Is "/data/misc/dhcp/" a persistent storage or would that directory be wiped after a reboot?

Edit: I'm asking the question because it seems that a new duid file is being generated for the people in question and the duid.c code clearly states "If we already have a DUID then use it as it's never supposed to change once we have one even if the interfaces do"
[ONE Original Android Development] Hilmesh:
Hello Just want to confirm. I am on Stock CM OS 12. So i should the following version right ? boeffla-kernel-3.0-beta8-CM12s-bacon.recovery.zip

Please confirm. and thanks in advance.
[ONE Original Android Development] dickenam:
Not sure if you want to dig deeper into the code, etc for this but if you search this thread for 'dhcp', there's a flashable zip out there somewhere that overwrites the current setup in favor of whatever it was for CM 11s. YMMV but, a few folks have had good results.

Thanks Andi!!!
[ONE Original Android Development] andip71:
This is correct.

Andi
[ONE Original Android Development] lchiocca:
I'm a developer - I don't like workarounds ;) I know that there is a flashable zip file that just replaces the dhcpd with the standard aosp version... hence the question to other devs out there
[ONE Original Android Development] dickenam:
Hahaha I just wasn't sure if you just wanted it fixed or if you wanted to fix it. Ya know? Sometimes we all just love immediate gratification :)
[ONE Original Android Development] alexbk66:
Yeah, me too, I find it pretty scary to simply copy some executable from the old OS version.
[ONE Original Android Development] lchiocca:
Especially if you know that the cm guys could actually cherry-pick 3 missing commits and they would probably get the issue solved.
[ONE Original Android Development] cr0wnest:
My phone deep sleeps just fine, however I noticed the drain even while deep sleep is pretty high at 3% per hour. I'm running on BlissPop ROM and I remembered the stock kernel fared better. I've tried the zzmove governor with the battery yank and battery plus profiles but both are about the same. I do not have any ZRAM, LMK, touch boost, or undervolting enabled. Could this be an issue with the ROM itself?

Other than that im really liking the kernel, its really smooth and stable! I've always loved your work. :)

EDIT: Oh forgot to mention, I'm running 4.0-beta16
[ONE Original Android Development] davebugyi:
Must be a rogue app or setting. Same kernel, Temasek unofficial CM12.1
[ONE Original Android Development] cr0wnest:
I just checked, it seems that under Alarms, Google Play Services is taking up a good percentage of it. Wasn't this issue already fixed in the 21st March CM builds? Or is this caused by something else?
[ONE Original Android Development] davebugyi:
It should be, because I do not have any.
[ONE Original Android Development] cr0wnest:
Thanks, I'll look into it. Perhaps its a rogue app like you suggested. I doubt its a BlissPop issue since its also based on official CM12.1 like yours
[ONE Original Android Development] andip71:
You have the known Google play store wake lock issue.

This is a combination of rom and play store version.

There are workarounds for it. I posted a link long ago to a thread.

Try to search, I am only on mobile and cannot dig it out.

Andi
[ONE Original Android Development] suaverc118:
I'm running the same ROM too but have high battery drain. Slept like a baby last night but earlier today when screen was off it just drained. And I too have high drain from play services even though I have keep awake and awake disabled. I'm also on the latest banks gapps as well. Grrr.
[ONE Original Android Development] laser03251:
Wifi issue

Hello,

I am currently on Blisspop 5/18 with boeffla kernel beta 15 ... I have found that my phone doesn't automatically connect to my home or school wifi network when it is in range. Going into wifi settings, it says that my wifi network is "saved" and if i tell it to connect it will then connect without a problem... however If i leave my phone alone for maybe 5 or 10 minutes, it automatically disconnects from my wifi network despite having "keep wifi on during sleep" set to "always." Never had this problem before using this kernel or blisspop any suggestions would be greatly appreciated

Thanks
[ONE Original Android Development] Sander9847:
I'm having The exact same problem with Blisspop 5/18 and Boeffla kernel beta 16 (5/18).

My phone doesn't automatically connect to saved wifi's.
[ONE Original Android Development] xflowy:
it's simply the rom. tested both with the exact setup. temaseks gives me the best battery life. blisspop the worst.
[ONE Original Android Development] TorchaOne:
And I have had this since 241 radio, whatever build or kernel. Sometimes connects but I you move a lot, away from wifi and back few times, it halts totally.

Edit: it wss DHCP problem. Assigned static IP and all good, at least at home... There was a fix somewhere for this?
[ONE Original Android Development] bloof:
[MENTION=947981]Lord Boeffla[/MENTION]

Hi Lord Boeffla, did you consider darkness gov? Nightmare is nice but a lot of people including me found darkness a really nice gov (over on LG G2 dorimanx side of things).

Cheers.
[ONE Original Android Development] darkangelism:
Do I need to flash kernel back to stock before switching from 12s to 12.1
[ONE Original Android Development] tsiftsism:
I'm using the 17/5 CM12.1 Nightly and since then i have a huge battery draining causing by MediaServer.

After some days without a Nightly release we have finally a new one so i'm downloading it right now in order to see if the issue will be fixed.

My question since i'm not familiar with the rom changelog is if there is something new considering the kernel and if there is going to be a new boeffla kernel in the hours to come.

Should i just flash the rom and wait for a new kernel, or should i flash the rom and after that the boeffla.beta.16?

Thanks in advance for your answers.
[ONE Original Android Development] andip71:
Beta16 works fine. Maybe a new kernel tomorrow, but nothing new would require it really.

So no strong plans as during weekends I try to avoid that.

Andi
[ONE Original Android Development] cr0wnest:
Ive the same problem here on blisspop running 5.1.1 but never had this issue with Exodus ROM that was running 5.0.2. I think its also worth noting that my Nexus 9 running 5.1.1 is also having the same issue (not official 5.1.1 from the factory image though) so Im assuming its an issue with 5.1.1. Does flashing the COS12 DHCP zip really fix the issue?
[ONE Original Android Development] anshumandash:
The Wi-Fi issue is a blisspop issue. They know about it and will fix it in the next build. Only thing is that right now we don't know when the next build will come as they are cleaning codes.
[ONE Original Android Development] mittimus:
Hi lord, I'm using boeffla saber version but i have a problem with GPS.. When I Try to set my position in Google maps or whatever it doesn't work.. It shows a fake position..

I'm with stock rom right now. Hope someone could help me
[ONE Original Android Development] ryaneu:
Hi Lord Boeffla.,

Any chance you can make a anykernel version so that your kernel can be compatible to most derivates of CM11?

Thanks
[ONE Original Android Development] andip71:
Sabermod version is not supported here. Ask in thread where you got it from..

In order to rule that out, have you tried stock kernel again, and then official Boeffla Kernel? To compare?

Not in my plans, no.

I was never a big friend of anykernel and will probably never be.

Sorry and thanks for understanding

Andi
[ONE Original Android Development] zodiaxe66:
Funny,i had a similar problem when i got opo,where the sound on my end was clipping and all around really bad and when my signal was low,others couldn't hardly hear me .

But i rarely use my phone for talk,maybe 5-6 calls a week(hate talking on the phone),so i havn't notized that the issue was gone and the audio actually is good and have been so for a while..

Maybe its a setting or 3party app issue.

Sometimes at work i kick up the volume to max,sounds stupid if that could fix it,but i haven't done anything to try and fix the sound issue,but gone it is..

Hope you get it fixed and soon..
[ONE Original Android Development] magnamentis:
well said & keep it that way :) first time that this phone works flawlessly and compared to reliability is on par with my nexus 5 on elementalX kernel. don,t say it was bad before but now it just works, something i usually can say only about my mac uuhhh... yes macOS is a different story from iOS which i despite for it's closed environment good job lord, this kernel met, even exeeded all my hopes

Sent from my A0001
[ONE Original Android Development] bkeaver:
Glad to see Lord Boeffla here on the OPO. Loved his work on my Samsung devices. This kernel has made my OPO supper smooth :) thank you
[ONE Original Android Development] NickosD:
Anyone else getting low scores at antutu? I know benchmarks doesnt matter, i am doing them for fun. The strange is that i can't go above 40k....

Performance is great, even at 1500/389 while playing ashpalt 8, and battery is great too.
[ONE Original Android Development] cerealguy:
Excuse me guys, I'm a searching a balanced value for touchboost... Default 1497 is a good compromise?
[ONE Original Android Development] Setting.Out:
Nearly every ROM I've tried, I get 45000+ on Antutu with this kernel.. I prefer slim/row
[ONE Original Android Development] Leicxan:
I got 44580 at antutu, I'm using zzmove with zzmove optimal profile
[ONE Original Android Development] f100cleveland:
I actually have mine set on 1190 and have great results. Also using zzmoove gov and battery - yank profile.

Since two cores are on all ready, boosting to 1190 upon touch has been plenty for me. Been debating on 1036 but haven't gone that low yet.
[ONE Original Android Development] jgcaap:
Anyone know where is the stock WiFi zip? Thanks
[ONE Original Android Development] P1nGu1n_:
#56194521
[ONE Original Android Development] nikeman513:
The restore WiFi didn't work. WiFi still won't turn on...
[ONE Original Android Development] adinkwok:
Flash the restore WiFi zip, then flash the kernel
[ONE Original Android Development] andip71:
But you know it is only meant to be for 38r cm11s, not for cm11 itself...

Just asking.

Otherwise you need to flash the rom over again, then apparently more has been broken...

Andi
[ONE Original Android Development] andip71:
Hi all,

usually I do not do kernel development during weekends (as weekends are fully dedicated to my family), however I feel I need to push out an important update this time.

CM11s and CM11 Boeffla kernels are now available as a new beta.

Version 2.0-beta5

26.10.2014

Important CM commit "msm8974: Stop breaking the whole system " included (might fix some hot reboot issues reported)

Only cm11s Boeffla kernel: WIFI drivers reverted back to XNPH38R stock for a test (as I saw some hot reboots in some kernel logs caused by WIFI)

Configuration interface /proc/config.gz enabled (important for developers and kernel porters)

As always, download from the homepage and flash in recovery, or just use load&flash functionality in Boeffla-Config for your convenience.

Cheers

Andi
[ONE Original Android Development] NickosD:
Damn.... Now I have to break my almost 3 days up time :P
[ONE Original Android Development] andip71:
Yes, I am sorry, you should. It is really an important maintenance update for improved stability.

Andi
[ONE Original Android Development] NickosD:
It's getting better and better.....

Btw update the date at title of the thread.