yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] JaylanPHNX:
I redownloaded v14 and tried again with the same result: no wifi. I took a logcat, but I have no idea if there's anything useful in here. Back to v12.

P.S. I added the .zip to the file name so XDA would let me upload it. Just rename it without the .zip.
[ONE Original Android Development] markvd90:
Anyone has a working UKM zip? Tried a few, all of them have some errors..

Kernel audiutor doesn't have all options :(
[ONE Original Android Development] JaylanPHNX:
[MENTION=5190317]fermasia[/MENTION], I just flashed fusionjack's latest upload and it works with v14. Everything is fine, now.

It's baconnn!
[ONE Original Android Development] webore:
just a quick question:

Why should the kernel have a wlan.ko in it ?

It makes the kernel huge .
[ONE Original Android Development] fermasia:
Well, it seemed like a fun prank when I did it, like making you guys download so many bytes just for fun! LOL :p

Or maybe not... and even when it shouldn't be needed to flash modules, we began having problems with wifi compatibility and the only way I could solve them was doing thtaa. I still didn't have time do dig further to fully understand the issue, thought. Meaning... might be no issue at all if Omni modified the way it's handling modules and if so it would just be about adapting the kernel to it, but may also be related to some other problem that gets solved with that procedure but may be better solved with some other action.
[ONE Original Android Development] KenjiHannya:
Donkey One Kernel v14 + SAOSP ROM 6.0.1 = amazing combo

https://plus.google.com/+JPKenji/posts/VFK6LGAk8hh
[ONE Original Android Development] Midzuel:
Can you link me the ROM?
[ONE Original Android Development] indian84:
Here

http://xdaforums.com/oneplus-one/development/rom-saosp-m-t3267790
[ONE Original Android Development] josera06:
This Kernel it's amazing with saosp!

I feel so sorry about your team [MENTION=5190317]fermasia[/MENTION], think you are subchampions of the world...

Enviado desde mi Bacon Machine
[ONE Original Android Development] webore:
Well , this can't boot with herna's latest 1217 build .the phone just go black after the 1+ splash screen.
[ONE Original Android Development] deepaklunked:
It works very well for me..
[ONE Original Android Development] :
Also running it. No issue
[ONE Original Android Development] usmani:
SOD. Please remove the.zip extension to open it.
[ONE Original Android Development] webore:
Thanks ,I'll reset kernel auditor and try again .
[ONE Original Android Development] fermasia:
Seems like that's Bricked Hotplug causing the kernel panic.

For now, the supported config will be the default, with CpuQuiet. I honestly don't find any solid reason to rework things into another hotplug driver, it's been working very well with Omni's stock + my optimizations, and I'm planning on keeping it that way. You may try switching to another cpu gov if you want to experiment further with Bricked if you want, thought.
[ONE Original Android Development] Tiz92:
Which app are you using for kernel settings? Synapse is not working, and i dont like Kernel Adiutor a lot.
[ONE Original Android Development] indian84:
There are quiet a few apps in play store. Hopefully you will like one of them. If not, you are out of choice.
[ONE Original Android Development] Tiz92:
Okay thanks, i hoped only someone has a good insider app :D If you know what i mean. Miss the boeffla app a lot in ASOP Roms.
[ONE Original Android Development] daltonhrrll:
I don't think all the settings appear in synapse
[ONE Original Android Development] :
Although I have no issue with Kernel Adiutor, since I would only under-clock and maybe enable power profiles, I find that Omni's Performance app works great.
[ONE Original Android Development] fermasia:
Yes, UKM is lacking some features for my kernel and Kernel Adiutor is missing charge levels and Adreno Idler functionality. But I've been really short of time to work on that (anybody willing to help with that, I'd be happy to work on it together).

That said, merry christmas to you all!!!
[ONE Original Android Development] JaylanPHNX:
Once time or resources become available, I'd like to see synapse supported, just because it can be better customized to the specific kernel. Until then, merry Xmas and happy New Year.

It's baconnn!
[ONE Original Android Development] fermasia:
As far as I've investigated, synapse + UKM is giving trouble in MM, and won't work as it used to, for now (there's wip). I'm uploading a new version of my UKM including some things, where the only things that are broken are: Adreno_Idler interface and GPU min and max freq controls, as far as I've checked. Can't promise settings will allways stick, and everything will work flawlessly, thought, for the reasons mentioned.

Still, Kernel Adiutor has almost every functionality you need, except for Adreno Idler and Charge_Level interface.
[ONE Original Android Development] fermasia:
Synapse is working, with some flaws, but it's working. You have to flash UKM (as instructed in the op) and then install synapse.
[ONE Original Android Development] JaylanPHNX:
Yeah, settings not sticking was the problem I had with synapse when I first tried on MM. And Kernel Adiutor works for most things. My only problem with it is that the gamma controls use a different numbering scheme and I can't quite replicate the settings I'm used to from using synapse and ak kernel on LP. A small thing, surely, but one I'm OCDing over for whatever reason. At least I have kcal adjustments thanks to your kernel. Merry Christmas!

It's baconnn!
[ONE Original Android Development] :
finally got round to testing v14, it also doesnt charge for me. The icon in status bar does change, in settings, about, status it says not charging. Battery percent also doesnt increase. I think the charging interface your using doesnt support all phones or third party cables.

Nikhils charging interface works. Maybe you can check wats missing in Omnirom and fix it for all of us?

It could also be the blobs used in rom.
[ONE Original Android Development] fermasia:
Sorry, nikhils?

I'm not sure I can solve it, probably won't... but let me know in what rom/kernel is charging working well for you, and if possible, some logs from when you are plugging the charger might help.
[ONE Original Android Development] KenjiHannya:
Nikhils is the dev of the Lightning Kernel
[ONE Original Android Development] fermasia:
Sorry, I knew about the kernel but didn't had his nickname in my head. The thing is that kernel is Ak Caf + his changes, and look like it accidentally happens to run with Omni (there doesn't seem to be any adaptation at all, as I believe he's not focused on making it compatible with Omni but making a CAF kernel).

Propperly importing sultan's CAF's charger logic into Omni is above my skills, and I'm not sure it's something we would want to. I believe it will be much more valuable getting some logs right after the charger has been plugged and fails to charge. And provide those logs to people that know Omni deep enough (like maxwen, samstone or herna) to narrow the search and try to see why non-original chargers are failing. I can have a look at those logs too... but I'm unsure I can help at all.
[ONE Original Android Development] :
I think its not chance, it anykernel format ;) that does wonders.

The logs show charge is set to 0 after first time its set to 1.

so I flash original rom kernel to clean, then lightning kernel and charging works. I fladh original kernel to clean then your kernel and no charging like on original. It would be nice if your use the charging interface he and ak used instead of the Omnirom one. It will work for all phones :)

I have no dev experience, but maybe a diff will show why this is so.

I did notice charging work on pre 6 omniroms, so I suspect the issue is somewhere from start 6.
[ONE Original Android Development] dinhvtai:
I'm getting bootloop when install this kernel on Slimsaber rom (based off Omnirom). Is it not supported?
[ONE Original Android Development] AmyClaraRose:
It's working fine with slimsaber for me

---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------

Using this kernel and my phone charges for me using slimsaber which is based of omnirom
[ONE Original Android Development] dinhvtai:
which builds are you on? I'm on the latest one of both Slimsaber and donkey
[ONE Original Android Development] AmyClaraRose:
Same latest 20th December build of slimsaber and v14 of donkey kernel
[ONE Original Android Development] dinhvtai:
These are my installed steps:

1/ Flash donkey

2/ Flash UKM

3/ Clear cache

4/ Reboot

And now I'm getting bootloop. Did I miss something?
[ONE Original Android Development] AmyClaraRose:
No it looks fine there only thing that I dint do which you did is clear cache I never clear cache when flashing kernels
[ONE Original Android Development] Brightlenny:
Dirty flash your ROM first then follow those steps
[ONE Original Android Development] fermasia:
No, no, anykernel just preserves the original ramdisk, but the code's still CAF and not Omni's. As for what I've seen in the git source, it's pure AK Caf with no adpatation to Omni whatsoever. So it does look like it's more of an accident that it's running with Omni (of course, with Caf's ramdisk it wouldn't work at all).

It's not that easy to import the charging interface, and would imply building a frankestein which might not be the best idea. Again, gather some logs, provide with your charger's specs and drop it politely in Omni's official thread to see if they can have a better clue on what's going wrong. Tag me if you like, and I'll have a look in case I can come up with something.

Edit: herna has just posted a new build with some tweaks on the chargwr interface. Give it a spin and let us know how it goes.
[ONE Original Android Development] fermasia:
I usually run stock Omni but wanted to try SlimSaber so now I'm on it's latest build plus v14. Cleab flash the rom and gapps, boot into it, then reboot into recovery and flash the kernel. It must work fine.
[ONE Original Android Development] dinhvtai:
Thanks for all of your support. I made a clean flash, I found that the reason for boot loops is gapps, I used the Banks Gapps. I switched to Open Gapps and no boot loop at all.
[ONE Original Android Development] jukiewalsh:
Non OEM chargers work, it just has to be a 2.0 A type fyi..
[ONE Original Android Development] :
mine is a 2.1a build to supply what phone can handle.

new Hena build also doesnt work. it goes on, and off, kinda funny really.

Oh well thanks for all your help:)
[ONE Original Android Development] tofu:
alucard?

Any chance to include Alucard CPU governor and Alucard hotplugging driver? It is praised for its battery friendliness.
[ONE Original Android Development] fermasia:
Version 25 released!

Hi guys, I'm here to announce a new version. Let's say this version will let us test a lot. For starters, I've brought up two new hotplug solutions and cpu governors; it's not my intention to keep 5 different hotplug drivers since I find that's excessive, I'm planning on keeping them for a few versions until we decide what gets to stay. Your opinions and suggestions are welcome. Main changes are:

- Introduce Alucard Hotplug driver + Alucard CpuGov (tuned for Omni -testing purposes)

- Introduce Blu_Plug Hotplug driver + Blu_Active CpuGov (tuned for Omni - testing purposes)

- Add State_Notifier with latests improvements by NeoBuddy89

- Introduce Franco's thermal driver (testing)

- Charger: tune voltage following Sultan's standard

- Further optimization of deadline sched gov

- Sched: improve wake-affine logic

- Many other small patches, bugfixes and micro-improvements (check the source for more information)

Link's on the second post... as usual :D

I've also made some small adjustments to UKM, there's a v2 available in the second post.

Enjoy, and please any feedback will be appreciated. :good:
[ONE Original Android Development] deepaklunked:
Downloading.. Just to test the alucard stuff.. :)

Edit: Installed. Testing now.

Edit 2: Alucard seems a bit laggy. At least when compared to Smartmax. Anyways, this is too early to tell. Will test intensely, further for another day..

Sent from my OmniBacon
[ONE Original Android Development] indian84:
Blue_Active FTW.
[ONE Original Android Development] KenjiHannya:
Test with Donkey Kernel + OmniROM

https://plus.google.com/+JPKenji/posts/hxvFiFuxvg5
[ONE Original Android Development] robbieast:
Is cpuquiet more battery or performance oriented??
[ONE Original Android Development] fermasia:
Wouldn't say CpuQuiet is, but the default kernel config intends to be balanced but leaning towards battery saving. But you have plenty of options to configure it your own way, for any purpose you want, changing governors, hotplug driver, battery oriented tweaks (power efficient workqueues, etc.). If you don't dare to change too many things, start testing different governors and/or hotplug drivers.
[ONE Original Android Development] fermasia:
Alucard and Blu_Plug are very new to me, I haven't used them in any of my kernels before. I tweaked them down a bit cause they were eating too much battery, but I'd apreciate if you want to test them, and if you find any tweaks (changing any parameters) that give you better results than the ones I used, I'd gladly take them into account for the next version.
[ONE Original Android Development] deepaklunked:
Hmm.. But I don't understand much about the tunables. May be Someone else could do it. BTW, I just woke up after about 6.5 hrs of sleep, and the battery only drained by 3%. I was amazed. I am still in alucard governor and hotplug. Will test for today and let you kknow how it runs.

Sent from my OmniBacon
[ONE Original Android Development] KenjiHannya:
Test with SAOSP ROM 6.0.1

https://plus.google.com/+JPKenji/posts/3SM7b4Wibna
[ONE Original Android Development] dinhvtai:
Can anyone share me the setting for amoled color by using Screen Control App by savoca (or Kernel Adiutor / Synapse), thanks so much
[ONE Original Android Development] KenjiHannya:
I do not know if it's amoled, but here is very beautiful.

Click in the link, What's Up ?
[ONE Original Android Development] deepaklunked:
[MENTION=5190317]fermasia[/MENTION]

Hi. Half battery cycle done. Alucard is nothing special in my experience.. It is still a bit laggy. I understand that its new to you, but it still needs to mature. So, the next half, I am going to test Blue_active. Will report back..

Sent from my OmniBacon
[ONE Original Android Development] indian84:
Here's my battery cycle.

BluActive Governor and Bluplug.
[ONE Original Android Development] deepaklunked:
[MENTION=4570506]indian84[/MENTION], which theme is that?

Sent from my OmniBacon
[ONE Original Android Development] indian84:
Here..

https://play.google.com/store/apps/details?id=bitsykolayers.MILOS
[ONE Original Android Development] deepaklunked:
Thanks. Will check it out.

Sent from my OmniBacon
[ONE Original Android Development] rsafford:
Can someone please link to the recommended settings for this rom? Beginning to not know the difference with the new governors.
[ONE Original Android Development] indian84:
You are in Kernel Thread. This is not a ROM.

Most of the Governor names are self explained and mention on page 1. For those like Alucars or blue active, you can find the info easily by Google.
[ONE Original Android Development] rsafford:
That was a typo. I haven't had my coffee yet. I am only asking because I know that s lot of these threads usually contain alternative setting for people like me who like to benefit from the experimental nature of others.

Right now, the only change I made was a switch to zzmoove.
[ONE Original Android Development] fermasia:
If others are willing to share them, you could try using synapse profiles (assuming they are working fine in MM, I haven't tried till now).

Stock config intends to keep the experience close to Omni's stock, just switching to Smartmax as default governor and using deadline as sched gov, plus activating all of the optimizations available in the kernel. What you could benefit of, are UV settings, govs and hotplug customization, and that could be easily share using synapse profiles as mentioned.
[ONE Original Android Development] rsafford:
Thanks. I will start messing around with the profiles this morning. I had been on Adiutor
[ONE Original Android Development] ogrillion:
Am I missing something with kernel auditor it doesn't seem to have all the hotplugs? It also seems when I change to say blu governor and turn off 2 cores it doesn't actually do anything.

I think it's not disabling the default hotplugs, cpu quiet? I don't even see that as an option. I assume I am being noob and missing something.

Edit: so googled a bit, and saw that on the initial cpu area it has a disable cpu quiet option, which lets me use whatever hotplugs I want.

I have downloaded this kernel app a handful of times and always deleted it because of the hotplug issue. Should have investigated the app a little more. I do think all the cpu hotplug stuff should be in the same section.

Thanks
[ONE Original Android Development] NexusPvn:
Out of curiousity, has the smartmax been pretuned or is it left alone ?
[ONE Original Android Development] fermasia:
No, it's not been modified at all.
[ONE Original Android Development] Bobbi lim:
[MENTION=5190317]fermasia[/MENTION] I've tried kernel auditor to configure smartmax_eps with stock CPUquiet settings and when I reboot the phone to ensure that settings are being applied correctly, a reboot gives me back a working phone. Whereas if I shut the phone down, turn it on again, after kernel auditor automatically apply settings on boot (takes 5s), my phone screen goes dark as if its powered off. Only way to get it to wake up is a force reboot by pressing and hold the power button.

Due to the scenario above, I've resorted to use Synapse but I can't get it to apply my settings on boot (it's irritating!) and I tried creating a profile/ configuration so that with the next boot up, I can just apply them but it turns out that the profiles were created correctly whereas I couldn't apply the profile/configuration with synapse behaving as if they weren't there.
[ONE Original Android Development] fermasia:
Yes, unfortunately kernel tweaking apps are giving us headaches in MM. For now, we can stay up to date with their developement following their own threads in Xda. Synapse is free & excellent in terms of flexibility and customization for every kernel... let's hope this non-sticking settings on reboot is sorted out soon.

If anyone has any suggestions regarding kernel tweaking apps, please share.

About your issue, I haven't been able to reproduce it in my phone (that black desd screen). But I'm using a testbuild of v15 which is in the oven right now, and I've made some changes that could have some effect on what you are describing. For now, those having issues, please stay off smartmax_eps until the next release.
[ONE Original Android Development] taufiqs:
[MENTION=5190317]fermasia[/MENTION] do i have to switch off cpuquiet if i were using bluactiv gov and hotplug?

[MENTION=5021085]Bobbi lim[/MENTION] i also cant reproduce the similar . I am using smartmax eps with kernel adiutor. The kernel config is permanent even after I shutdown the phone. Instead, GPU adreno idler's config is the one which is not stick.
[ONE Original Android Development] fermasia:
Yes, having both cpu_quiet and any other hotplug driver enabled at the same time is notna good idea.

About Adreno Idler in Kernel Adiutor, the switches are not working but it's on and running. When you "enabled o disable' it from the app, it has actually no effect on the sysf. I should have a look at Kernel Adiutor's code and try to adapt the sysf to it.
[ONE Original Android Development] taufiqs:
Oh yeah one more thing, i also cant switch suspend mode. Always went back to autosleep.
[ONE Original Android Development] fermasia:
I know, it's intended to function that way. Powersuspend is under review, to decide if it should or should not stay... since is arising some troubles and I'm beggining to think we will be better off it.
[ONE Original Android Development] skyhonor:
Hello,

Should I flash your kernel with fusionjack's [ROM][6.0.1][12/26][OMNI] SlimSaber - find7op (aka bacon)?

Thank you in advanced.
[ONE Original Android Development] deepaklunked:
If you want.

Sent from Simplified Bacon
[ONE Original Android Development] JaylanPHNX:
That's the combo I'm using.

It's baconnn!
[ONE Original Android Development] Vishalkris:
Kernel doesn't support USB otg. Phone freezes and have to reflash the basic kernel to get otg acess.
[ONE Original Android Development] fermasia:
Hey, can you provide me with some logs about the issue? Plus check your pm inbox, if you don't mind I've sent you something for you to test for me. Thanks and happy new year :good:
[ONE Original Android Development] Vishalkris:
[MENTION=5190317]fermasia[/MENTION] I just saw will report after testing

---------- Post added at 12:54 PM ---------- Previous post was at 12:34 PM ----------

It didn't work...the test version BTW I'm on SAOSP but the base kernel is omni kernel and with the base kernel it works flawlessly... On this kernel the moment I connect otg screen stops responding sends later screen go blank and refuse to awake also the power to otg goes away...tried with flash drive,card reader,Bluetooth dongle for Logitech gamepad...doesn't work at all...thanks for the test version for me...;)
[ONE Original Android Development] fermasia:
Yeah, I know. There's something in one or two commits from the 400 I've added to the stock kernel, that's conflicting with OTG, but I haven't been able to spot it. And to make things worse, I don't use any OTG device to test it myself... so, even if I get to solve it, it will take some time.
[ONE Original Android Development] Startlinger:
well, perfect, Combi Herna and this Kernel
[ONE Original Android Development] mada1991:
First of all thousand thanks for your great work...

but...

Yesterday I tried to upgrade your kernel from V14 to V15 but my OPO after that it wasn't able to boot... It stayed on the boot 1+ logo....

I've tried a completely clean install with Omni (herna) Rom (26-12 and 17-12 version) but nothing...

I've revert to V14 and my OPO returned to work find...

Am I the only one?
[ONE Original Android Development] FunkyRasta:
LOL the same. V15 works flawlessly on my OPO with Herna's OMNI but refuses to boot on brother in-law's OPO. Exactly same zips !

So maybe voltages ? Has stock voltages been touched ?
[ONE Original Android Development] mada1991:
Are your two OPO the same?

Let me explain better...

Both of them have or haven't the cyanogen logo on the back?
[ONE Original Android Development] FunkyRasta:
Both are fairly recent. Mine was bought in July, his a month later. Both straight from OP website and do not have CM logo on the back
[ONE Original Android Development] mada1991:
They should have some different like mine...

It goes over my knowledge....
[ONE Original Android Development] Startlinger:
update on standby

http://xdaforums.com/showthread.php?p=64674112

its amazeballs
[ONE Original Android Development] dead0:
ive also had the same issue with saosp, v14 boots but v15 stuck on the 1+ logo

my one does not have the cyanogen logo on the back even though it came COS from opo direct
[ONE Original Android Development] mada1991:
I think so, there are two versions of One...

When Oneplus's solved the problem of the yellow screen band and the extra low volume of the audio capsule, they should have made some others changes to the hardware...
[ONE Original Android Development] Startlinger:
guys update the firmware to the recommended version of the rom, use twrp 2.8.6.0 or compatible :)
[ONE Original Android Development] MBurns2:
i want to be sure that i'm using only one hotplug.

Looks at my screenshot pls, i did it right ? i want only to use alucard. Thanks
[ONE Original Android Development] kalapapa:
Yah you are just make sure that its working properly. Do this by seeing what cores are running and see if they unplug and hot plug properly. If you think it isn't working properly then change cpu governor and change back and it will work fine