yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] kodora:
[MENTION=5190317]fermasia[/MENTION] on point! This is a developers forum.. That's why the posts need to be about constructive criticism and if possible technical reports.

The whining I see in a lot of threads is just a waste of time, since without good info a developer can't do nothing. (rant off.. lol)

Having said that, now I can say that after tuning your kernel with omni and my usage, I already got to the levels of Lollipop. About 2, 2.5 days or 7 hours screen on of battery. Thank you for your good work!
[ONE Original Android Development] :
Mind sharing your settings.
[ONE Original Android Development] :
thanks bro, this made my day!

I will test charging tommorow on your kernel, after I am done testing Hernas build :)
[ONE Original Android Development] fermasia:
Thanks. The new build is a bit delayed (need to debug an issue I ran into) but will probably be ready today or tomorrow.
[ONE Original Android Development] usmani:
Would you fancy a feature request? I'd like to see how msm mpdecision works with omni. Can you include it as an experiment?
[ONE Original Android Development] fermasia:
I'm already having a look at it, but won't be in immediately (not in this build I'm planning to release today or tomorrow). Most probably in the following release.
[ONE Original Android Development] kalapapa:
OK so as I've seen people saying that the latest Omni rom breaks wifi. I went about and unzipped the kernel files and replaced some of the files from the official boot img and it fixed wifi and all the governors and customization is still here. I added the zip in the attachment t. I tested [MENTION=1228651]fusionjack[/MENTION] Omni builds but not on the builds by herna. Try it for yourself and see if it works. This is absolutely none of my work. All credit goes to [MENTION=5190317]fermasia[/MENTION] and Omni devs. I will not provide any support for this as I am a complete noob. Please share if you want.
[ONE Original Android Development] pa.pn2:
No wifi for me. Jfyi
[ONE Original Android Development] kalapapa:
Are you using fusionjack build or official nighlies

I tested on fusionjack builds
[ONE Original Android Development] pa.pn2:
Official builds..
[ONE Original Android Development] kalapapa:
I guess it doesn't work with it properly
[ONE Original Android Development] fermasia:
V11 released

I finally found some time to find out what was going wrong, and the new version is ready. You'll find the link in the second post as usual :D

Changelog:

- Added Bricked Hotplug (disabled by default)

- Build with linaro/GNU 5.2 toolchain + new flags

- Re-added Smartmax_EPS

- Fixed voltage control issues

- Updated MDSS

- added franco's thermal control + Derromtester's tweaks (testing)

- added vibration levels control sysfs

- added sysfs entry for CDROM/USB emulation toggle

- Many other tweaks and fixes
[ONE Original Android Development] fermasia:
Even when I need to have a better look, it seems there's been some changes in how Omni's builds handle wifi modules, that's what was messing up my previous kernel build. It's solved in this new release (v11).
[ONE Original Android Development] usmani:
Hey fermasia, I'm seeing cores and frequency getting stuck. I'm using msm mpdecision right now. This also happened on stock kernel. It happens some time after screen on.
[ONE Original Android Development] usmani:
On stock kernel it happened when I tinkered with hotplug.
[ONE Original Android Development] usmani:
With cpuquiet on stock kernel I just changed min cores to 2 rest was stock. This is what I'm using right now in msm mpdecision.
[ONE Original Android Development] fermasia:
I'm not sure I fully understand what you are saying: what does "tinkering with hotplug" exactly mean? And from your pictures, should I conclude the problem is that one of the cores won't get any lower than 1267200?

If that's so, I haven't been able to reproduce what you are describing. Please if someone else runs into a similar situation please let me know.

P.D. For future reference, please try to consolidate your posts. You can make just one by editing. and it helps to make the formu more readable i think.
[ONE Original Android Development] usmani:
Tinkered with hotplug means I changed min 1 core to 2 cores in cpuquiet. one of the cores won't get lower and all cores remain online. And yes they don't go offline.
[ONE Original Android Development] fermasia:
I tried using Interactive CpuGov, setting CpuQuiet's min_cpu cores to 2, and I can't get any stuck core (I assume msm_mpdecision was off when you had CpuQuiet on, right?). I'll try a few fixes on the next release and see how it goes.
[ONE Original Android Development] usmani:
Yes, with cpuquiet it was on stock kernel. Now I'm using your kernel with msm_mpdecision and interactive. Try my settings from the above screenshot. It happens randomly, after 10 to 20 mins.

It could be that synapse is the culprit. Are you using it too? How are you configuring the tunables?
[ONE Original Android Development] Xerosnow:
He suggested kernel adiutor.
[ONE Original Android Development] budbay:
[MENTION=5190317]fermasia[/MENTION], thanks for trying out the cdrom/USB emulation. it is working perfectly with drivedroid . I was able to switch between modes perfectly. only been on v11 for a couple hours but everything seems to be working well using kernel adiutor. on last version with stock doze settings I only had between .2% to .4% idle drain overnight. can't wait to see how well this one performs. thanks again and keep up the awesome work.
[ONE Original Android Development] DerRomtester:
I hope you did not pick from my omni branch. I have made a mistake there. So the thermal driver did not throttle at all. I had no time yet to figure out what i did wrong.
[ONE Original Android Development] usmani:
I think I'm able to reproduce it now. It happens when I'm using cpu boost and some heavy tasks are being done, which utilize four cores . The frequency gets stuck to input boost value. Before I was using smartmax without cpu boost driver and it did not happen.
[ONE Original Android Development] bkayy:
Can i use this kernel on broken os?
[ONE Original Android Development] fermasia:
Thanks for the heads-up. As I quoted I was testing it, i'll revert it and carry on testing other options.
[ONE Original Android Development] fermasia:
Ok, then i have some clues on how to solve it. Will probably be sorted out on the next release. Thanks.

If Broken OS is omni based, you can try.
[ONE Original Android Development] erad1:
It will boot but WiFi will not work. Tested already.
[ONE Original Android Development] fermasia:
It's CAF (Sultan's) as I've just checked. So no, it shouldn't work.
[ONE Original Android Development] devilsshadow:
Is this compatible with Omni 6.0.1?
[ONE Original Android Development] kalapapa:
It worked for me
[ONE Original Android Development] fermasia:
Should work, unless samstone has added any conflicting kernel commit that's not yet published in the official source, since my kernel is based onto it.

I'll test it myself too, since I want to see if the next version of my kernel (which will be out very soon) works fine with it.

EDIT: as it's been confirmed in Omni's testbuild thread, they follow the official Omni sourcecode, so this kernel should work fine with the recently published 6.01 build.
[ONE Original Android Development] qwerty123321:
Just wanna thank you for creating this kernel. With it, I am able to adjust the vibrator strength.. The default 100% is ridiculously loud !
[ONE Original Android Development] clock51:
it works well for me
[ONE Original Android Development] fermasia:
V12 released !!!

Hey everybody, a new version is out! Link's on the second post and many changes are included:

- Updated MDSS

- Fixed buggy voltage control

- Added and tuned up Adreno Idler (enabled by default)

- Built with UBER 5.2 optimized toolchain and added some new flags

- Enabled more TCP congestion govs

- Retuned ZEN sched gov

- Upgraded to linux 3.4.109 (massive thanks to fusionjack) and synced to slimsaber sources to ensure compatibility

- Many more optimizations.

I've given it a few days testing and I'm very pleased about the result. For sure it can still be improved, but I think it makes a really inetresting combo with official Omni, herna's builds and fusionjack's slimsaber (and probably to any other omni based rom out there).

Hope you like it and I'd appreciate some feedback on the performance.

Cheers to you all :good:
[ONE Original Android Development] venky716:
Have been running it for almost 9 hours now, must say has been very stable and super smooth. Thanks

Also does zen hotplug and zen scheduler go well together or is it just the name ?

PS: Found it by chance on androidfilehost while browsing :D
[ONE Original Android Development] asanuma:
Hi [MENTION=5190317]fermasia[/MENTION], I installed V11 onto Omni slimsaber 6.0.1 (fushionjack) 12/9 build then USB OTG didn't work and the phone switched off suddenly.

Does donkey kernel support USB OTG? Sometimes I use USB flash disk for file transfer.

Thanks.
[ONE Original Android Development] fermasia:
Try v12 and report back, please. Does usb otg works well with slimsaber's stock kernel?
[ONE Original Android Development] rucioTozzy:
sorry, v12 otg doesn't work and force shutdown. slim original kernel work.
[ONE Original Android Development] fermasia:
All right. I have some suspects to check, but some logs would be very useful. A last_kmsg right after that reboot happens, and just in case, the rest of the logs too if possible.

Thanks :good:
[ONE Original Android Development] asanuma:
USB OTG works well on Slimsaber's stock kernel.

Thanks.
[ONE Original Android Development] :
did you by any chance change the charging interface in the new kernel?
[ONE Original Android Development] HaTrED_:
[MENTION=5190317]fermasia[/MENTION]

There you go mate : https://db.tt/fxONkquh

After inserting an otg pen, system froozed and rebooted afterwards!
[ONE Original Android Development] clock51:
I installed the v12, works well, but can not find the tab for setting sounds, it has been eliminated?
[ONE Original Android Development] fermasia:
Not the interface but there were some optimizations included, what did you notice?
[ONE Original Android Development] fermasia:
It was pulled cause I'm trying another option, so on the next release we'll have it back, or replaced by something i think will be better :good:
[ONE Original Android Development] venky716:
Charging was slow in my case.

Took around 90 mins to charge 50% usually takes around 50-55 mins. Stock charger and cable, usual Oneplus (not the Chinese version)

I don't really mind slow charging since phone stays cool, will test again in next cycle.

SAOSP and v12.
[ONE Original Android Development] fermasia:
Yes, for some reason it seemed to be triggered into fast-charge by default. On my end, I prefer a normal charge time since I believe it contributes to battery's health (I know that can be argued, thought). I may add a fastcharge option in the next release so each one can choose how they like it.
[ONE Original Android Development] JaylanPHNX:
That would be great. One thing I miss from ak on 5.1.1 was being able to crank the charging rate up to 2+ amps when I needed a quick boost, and turn it down to slower charging for overnight. Thanks for a great kernel that works well with the new omni-based SlimSaber.

It's baconnn!
[ONE Original Android Development] KenjiHannya:
Lets test with SAOSP ?

Tnx ?
[ONE Original Android Development] kalapapa:
Could you give me the link to the forums and download for bacon

Thanks
[ONE Original Android Development] shuini:
performance－ voltage

Adjust the voltage does not work。

Thank you for your work！
[ONE Original Android Development] fermasia:
I'm actually testing if it brings any actual effect or of it's just placebo.

Yeah, it's using cpuquiet. I had mixed feelings at first cause there was some strong "google services" drain in stock kernel, and at the same time some slight stutter I thought could be due to cpuquiet routines. I'm now testing how it interacts with other hotplug drivers, and also testing other govs besides the default load_stats. So, I'm sorry to say I don't have a clear opinion about it yet.
[ONE Original Android Development] fermasia:
Version 2.0 - Released!

New version (2.0) released. Link's on the second post. Coming with many new features and optimizations:

Changelog Version 2.0 - 23-Feb-2015

- added new KCAL Control by [MENTION=4316709]savoca[/MENTION]

- added Faux Sound

- added Voltage Control

- added MSM-MPDEC (Bricked) hotplug

- added toggle in UKM to enable/disable CPUQuiet hotplug driver (and updated to V3.7 thanks to apb_axel)

- updated touchscreen driver

- updated governors

- re-tuned all hotplug drivers

- compiled with new flags & Graphite (testing)

- and more (check my git source for further details)
[ONE Original Android Development] fermasia:
In case you are still interested, I should say that after a bunch of testing rounds, it seems pretty interesting to me. With some simple tweaking (mostly about relaxing hotplug steps) gave me good performance and a very reasonable battery drain (with a slightly tuned Ondemand gov). Yet I didn't have time to try adapting it for powersuspend (if that's possible at all, haven't even got a good look at that yet).
[ONE Original Android Development] DerRomtester:
Yeah i am still interested in it but it is difficult to implement on cm kernel source.
[ONE Original Android Development] fermasia:
Yup, I could imagine that... lol. And having a bunch of hotplug drivers to choose from, even if possible to implement, I'm not sure sweating to achive that is the best idea.
[ONE Original Android Development] fermasia:
Developement halted for now

Lol, I knew Omni wasn't the most popular guy in this block, but I didn't expect so little attention. Not that I need a crowd or anything, but the time and work needed to move this project forward doesn't seem proportioned to the very very few people interested in it. So I'm deciding to halt this until Omni hits official lollipop nightlies - when perhaps this might become useful to more people.

Cheers :good:
[ONE Original Android Development] skeetzor:
As soon as omni goes nightlies I'll be moving from euphoria
[ONE Original Android Development] daryelv:
I love Omni, I just wish there was more official support for my OPO.

-Daryel
[ONE Original Android Development] fermasia:
Well, yes. But at least Omni tries to do something different. I see no point in SO many working on CM clones whilentrue alternatives like this one are lacking man power.
[ONE Original Android Development] daryelv:
Very true. I've thought about working on merging in the code to support the new blobs. CM makes compiling and building roms easy. Pulling in cherry picks to add functionality is very easy. But to understand the framework and be able to deal with code conflicts takes some serious work. There are some pieces that CM has implemented with Lollipop that I like. The root access security is nice to have in the Privacy area is one example.

-Daryel
[ONE Original Android Development] störte:
HI. Is this kernel only for the 5.02 ?

Would like to try it on 5.1
[ONE Original Android Development] fermasia:
There are some commits missing, I'm not sure if it will work. And if it works it will probably brake something.

But well, I can update it during the newt few days if there's interest in it.
[ONE Original Android Development] NuLLV01D:
Would love it
[ONE Original Android Development] fermasia:
I'm testing right now a new updated version. Once I'm sure there are no important bugs, I'll share.

There's some power drain that's that's presentsince the first lollipop builds (I think [MENTION=905572]scanno[/MENTION] is looking into that, at least I've seen him comment about it) and I'm trying to compensate with some battery saving features.

Hope I have it ready in a few hours. :good:
[ONE Original Android Development] störte:
Great. Will try it with Darkobas Rom
[ONE Original Android Development] fermasia:
No man, this kernel is exclusively for Omnirom, don't try it on any CM based derivative like Darkobas.
[ONE Original Android Development] tmimaesk:
AFAIK Darkobas is based on Omni for 5.1 since other cm 12.1 kernels won't work. If you release the new version, I would love to test it.

Thanks for all the hard work!
[ONE Original Android Development] fermasia:
My bad then, las time I checked Darkobas was baseed on CM, but seems that from 5.1 he's swapped to an Omni base. Good to hear that.

I have my v3 (5.1) alpha kernel ready for you to test, I'm posting it right now.
[ONE Original Android Development] fermasia:
NEW!! Updated 3.0 alpha version released - for 5.1 Omni

Guys, here's my new alpha version supporting 5.1 - reworked from scratch, added many updated goodies.

I'll very much appreciate your feedback about it. Didn't have time to give it a few battery cycles, so I'd specially like to know how's battery life. I'm starting with a defaulted Slim gov + Bricked Hotplug combo, but toy around with the options and if you find a better combination, let me know. There's some battery leaking in Omni since we went Lollipop, but I've pushed as far as I could without compromising performance to balance it and get a reasonable output. There might also be some drain in Google Play Services that's harsh to contain without having AppsOps enabled to refuse some permissions (there are other workarounds I'm testing myself).

That said, these are the changes:

Version 3.0 alpha - 04-Apr-2015

- Rebased onto 5.1 Omni source

- Compiled using UBER 4.9 toolchain

- Using Bricked Hotplug (thanks to ak) and tuned CPU Quiet

- Added Power Efficient workqueues (thanks to RenderBroken)

- Updated QuickWakeup (thanks to RenderBroken)

- Kept KCAL v2 by savoca, Faux Sound and Powersuspend

- Replaced thermal manager with franciscofranco's simplified driver

- Added Impulse CPU gov, kept YankActive and IntelliMM

- Many other optimizations (check my git source)

Enjoy!! :good::good:

EDIT: Updated UKM (check the second post) to the latest version including the mod to toggle on and off CPU Quiet Hotplug Driver.
[ONE Original Android Development] KenjiHannya:
Yes, sure

https://plus.google.com/+JPKenji/posts/dJqzuZBW7cL
[ONE Original Android Development] KenjiHannya:
This?
[ONE Original Android Development] shuini:
yes,But I did not install Synapse.Just use the stock.

I'm not good at English，I hope you can understand.

Thank you
[ONE Original Android Development] clock51:
try installing app "Kernel Adituor" works very well, find it on google play
[ONE Original Android Development] KenjiHannya:
No problem mate ?

Try Kernel Adiutor, is the best for a daily user ?

Cheers
[ONE Original Android Development] fermasia:
I can't support a ROM that's off Xda limits, has no public source, and I can't be sure what's based onto. Unless all what I mentioned is not in the G+ account and can be found elsewhere. Till then... :(

Indeed, I never used the inbuilt performance control voltage regulator, and as you say, it doesn't work. Yet... you would have to change every step's voltage manually, one by one, I think. Use kernel adiutor, as they've suggested some posts before, I've tested voltage control with it and works well.
[ONE Original Android Development] venky716:
SAOSP ROM, it's indeed on XDA with source,

Also so far Donkey works well with it since OMNI base.

http://xdaforums.com/oneplus-one/development/rom-saosp-m-t3267790
[ONE Original Android Development] shuini:
ok.

Thanks

---------- Post added at 12:06 AM ---------- Previous post was at 12:05 AM ----------

ok. understood.

Thanks
[ONE Original Android Development] fermasia:
Good to know, the user linked a G+ profile, but I'll have al ook. Thanks.
[ONE Original Android Development] KenjiHannya:
[MENTION=2555115]farmacia[/MENTION] SAOSP 6.0.1 + Donkey One Kernel is a good combo. I get a good SOT ??
[ONE Original Android Development] anbinhv:
How is good mate?
[ONE Original Android Development] KenjiHannya:
10% battery used = 1:00 ~ 1:15 SOT
[ONE Original Android Development] pumaworld:
Multirom support?
[ONE Original Android Development] fermasia:
Not yet ;)
[ONE Original Android Development] fermasia:
Seems like maxwen pushed a commit that is supposed to solve Omni not booting on some phones.

If anyone wants to try... I can add it and compile a test-build later today.
[ONE Original Android Development] fermasia:
Version 14 is up!

Hi everybody, a new version (14) is up. Yes, the number is 14... I don't like the 13 too much, and today the football team which I'm fan of had an important match, so...

Back to business, here are the changes for the new version:

- Maxwen's commit "solving" the non-boot issue on some phones has been merged and included in this build, please report back.

- Updated Uber Toolchain to 5.3

- Updated linux version to 3.4.110

- Added LMK (low memory killer) optimizations (thanks to renderbroken for his work on this)

- Added some charger tweaks from Sultan's CAF source

- Added Charge_Level interface (for those who know what they are doing!) - I had no time to tweake UKM script to handle it, so for now you had to manually edit the sysf file (with any root capable file explorer) - indications are on the third post, but again, proceed with caution if you don't know what you are doing.

- Readded Franco's sound driver (haven't found anything better for now)

Enjoy and feedback will be appreciated. :good:
[ONE Original Android Development] clock51:
no problem with the V 14, works perfectly, the rom fast starts, returned also the tab to set the sounds, thanks [MENTION=5190317]fermasia[/MENTION]
[ONE Original Android Development] ten_tickles:
Hi, it doesn't seem to download as a .zip file.

Is it just me?

Thank you.
[ONE Original Android Development] clock51:
you must rename to .zip
[ONE Original Android Development] ten_tickles:
Apologies for being stupid...slightly embarrassing.
[ONE Original Android Development] fermasia:
Sorry, my bad. There was a typo in the filename. I've reuploaded the file with the correct name. If anyone already downloaded the wrong named file, you just need to add the ".zip" to it.
[ONE Original Android Development] fermasia:
Would you try again with v14 and let me know if the problem is still there?
[ONE Original Android Development] HaTrED_:
Will do!

By the way, link to your latest version in op is pointing to V12...
[ONE Original Android Development] fermasia:
I definately need a good night sleep today... LOL. Solved :good:
[ONE Original Android Development] HaTrED_:
Well mate, it's a no go... [emoji20]

https://db.tt/V5Khmscz
[ONE Original Android Development] evertking:
Just flashed and it boots fine. Thanks for the kernel!!
[ONE Original Android Development] JaylanPHNX:
Did anybody else lose WiFi after flashing v14? It wouldn't turn on at all. Going back to v12 fixed it. Maybe [MENTION=5190317]fermasia[/MENTION] should've gone with the number 13 after all.

From my SlimTab Pro 8.4
[ONE Original Android Development] fermasia:
What rom (version) are you flashing onto?
[ONE Original Android Development] KenjiHannya:
With SAOSP ROM, Donkey One Kernel is perfect for me.

1:00 battery used = 1:10 SOT
[ONE Original Android Development] JaylanPHNX:
Sorry, should've known to include that. Latest omni-based SlimSaber. Is there any specific log that would be helpful?

It's baconnn!
[ONE Original Android Development] venky716:
Same setup here and WiFi is working fine for me.

Slimsaber 13 Dec

Donkey kernel v14
[ONE Original Android Development] fermasia:
[MENTION=3195615]JaylanPHNX[/MENTION] have you solved your problem then? I was about to suggest something, but if it's working in another phone with the same config, it must work on your's too. Let me know how it goes.
[ONE Original Android Development] fermasia:
Well, at least the log is clearer about what's going wrong. Yet I'm not sure if I can solve it right now. You said the reboot is triggered by the insertion in the port, right? I mean, the phone freezes and reboots right away, right?
[ONE Original Android Development] HaTrED_:
After inserting otg pen, the screen goes black and phone becomes completely unresponsive! You have to hard reboot it...
[ONE Original Android Development] fermasia:
Ok, I'll analyze further. Thanks for the feedback.