yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
Here you go and I also overhauled LMK/OOM.

Download R1-T4 for Android M
[ONE Original Android Development] MBurns2:
Render, are you still using msm hotplug+smartmax with gianton profile? Thanks :)

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] RenderBroken:
Yes, a form of it. I have changed the SmartMAX Values accordingly and removed all boosting from the governor to allow for CPU-Boost only to boost. So far I have been very impressed. I have tested out all other hotplugs and still believe MSM_Hotplug to be superior but others may argue that point. I also plan on testing other hotplug designs like Zen_Hotplug and Mako_Hotplug.

Work has been keeping me very busy so I have not been as active as normal. But I see that changing in the very near future.
[ONE Original Android Development] DarKAngel1234:
Been using your Kernel M-R1-T4 the last few days on Sultanxda's CAF CM13 build from Nov 14. I must say amazing, I couldn't get synapse to work at all because of root issues and UKM also not working properly, I used Kernel Auditor to tweak the kernel, turned off CPU boost, using MSM_Hotplug, and I/O SIO, undervolted slightly, buffer 2048, also limiting CPU speed to 300-1574, also put in xpossed V77 using greenify, naptime, amplify. Idle drain is down to .7 Volts per hour in standby. Simply amazing results bud.
[ONE Original Android Development] RenderBroken:
I have to agree with you. With the new LMK changes I made, I have not had to restart my phone due to low ram. LMK is working as expected and memory leaks are down to a minimum. Very happy with this start. I plan on making this my base for Android 6.0
[ONE Original Android Development] DarKAngel1234:
I have also noted that it will not Lock in the frequency's to limit it to only say 1574, it will often go above to other frequency's.

Not sure if this is Hotplug activity or what?
[ONE Original Android Development] xflowy:
hey guys! can i flash r8 test kernel on aosparadox? thanks!!
[ONE Original Android Development] RenderBroken:
I remember the fix I had to use for CM12 CAF Source. It will be fixed for the R1-Final build.
[ONE Original Android Development] kodora:
With MSM hotplug I only have one isue.. Don't know if its related with that, but sometimes when I wake up the screen I only get one active cpu and frequency is limited to the one I limit for screen off. Any ideias how to turn this around? Also I am using zzmoove governor.
[ONE Original Android Development] Renosh:
The kernel is amazing really smooth and great performance but there's one issue I keep experiencing, randomly when I turn on screen (happened twice so far) the screen doesn't turn on but it seems like it has, the buttons are lit up and long pressing the power button has a response but otherwise can't do anything unless I reboot.

I am not using UV, just underclocked to 1.7 GHz and lowered boost and sync threshold
[ONE Original Android Development] spr33:
I've just converted over to CM13 (Sultan ROM) and I'm very happy with the current performance. Is performance definitely a significant improvement over stock?
[ONE Original Android Development] vjsanjay:
Any more updated test builds "R8 CAF for cm12.1"
[ONE Original Android Development] RenderBroken:
Could be conflicts from zzmoove. Try a different governor to test this theory out and let me know. Thanks!

I am going to say that this sounds like its possibly Rom side. I have the issue where sometimes when you turn the screen on the touch is not working. I have to turn it off then back on to reset it. But I have not experienced this issue with CM13. Does anyone else have this problem and believe it to be my kernel?

Thanks for the report!

Yes.

I get better performance (Smoothness) and battery using my own kernel over stock. MPDecision from QCOM is a bit overzealous in my opinion.

No test builds, just a release coming soon but it will most likely be the last CM12 CAF build I do. Thank you for your interest!
[ONE Original Android Development] kodora:
[MENTION=5438598]RenderBroken[/MENTION] will do. I just began testing with smartmax, and for now all is good. I will try to read a bit about zzmoove tunables to see if I can overcome the issue. Any conclusions I'll be reporting here. [emoji4]

Bacon sent
[ONE Original Android Development] spr33:
Installed the initial M kernel and it is very nice indeed. I've reduced the max clock freq to that of Sultans ROM and it's definitely noticeably smoother. Animations are buttery and app loading times seem better.
[ONE Original Android Development] xflowy:
any news on new version? :)
[ONE Original Android Development] shubham1120:
Yep happens to me too. The touch sometimes doesn't work when screen is turned on. Definitely a rom issue. I haven't experienced this on 18th Nov build though.
[ONE Original Android Development] RenderBroken:
Yea, I am trying to find tie to finalize it. I had done a crap ton of testing with the mainline branch so I need to consolidate it all.
[ONE Original Android Development] xflowy:
good to hear man. looking forward to it? is there or will you implement zen decision?
[ONE Original Android Development] sas.mar:
[MENTION=5438598]RenderBroken[/MENTION]

Hello, could you please add f2fs support if it's possible at all?
[ONE Original Android Development] kodora:
Hey [MENTION=5438598]RenderBroken[/MENTION], remember that I had that issue with zzmoove and MSM hotplug limiting the cpu frequency to the one I set on MSM limiter? Well.. After some reading and a bit of testing I solved it!

First of all, with zzmoove we don't need MSM limiter, so I disabled it. Apparently zzmoove has its own screen off frequencies and a kind of hotplug hardcoded. To edit some of this values it was needed that those ones were accessible via ukm. But for now, all is well and I am getting the results I expected! Last night with Wi-Fi on only lost 1% in 8h.. So, I can't complain and only have to thank you for your work!

Bacon sent
[ONE Original Android Development] Renosh:
[MENTION=5438598]RenderBroken[/MENTION]

Which UKM works with your r21? I'm trying to change CPU frequency using Synapse and I keep getting a "SSeekbar bar has failed". I'm using it on COS12.1
[ONE Original Android Development] RenderBroken:
Most likely you are getting conflicts from AK's UKM. You will need to use his uninstaller fist then flash my UKM.
[ONE Original Android Development] Renosh:
I've never flashed AK's UKM I downloaded from the OP. Tried 3.8.1.4/2/1 none of them give me access to the CPU frequency but everything else works. And I remember you had issues with older versions of your kernel not accepting changes to frequency did you update r21 since you moved to CAF? Also any voltage changes result in reboot
[ONE Original Android Development] RenderBroken:
It is included with his kernel now so if you are flashing my kernel on top a flash of his, you will get errors. With R21. I had no such issues using my version of UKM. And with the Voltage changes, some others were having issues with other kernel editing apps causing conflict and they had to be removed.
[ONE Original Android Development] Renosh:
I haven't used AK kernel in months. I was on Boeffla kernel + latest COS 12.1. Boot to recovery flashed his reset zip. Boot to bootloader and reflashed system+boot and reboot. Boot to bootloader again flash recovery and flash TWRP, boot to TWRP and flash your kernel + UKM. Is there something additional I should be doing? I repeated flashing the images when I wanted to flash different versions of UKM
[ONE Original Android Development] RenderBroken:
Its hard to say at this point. I am unsure if your procedure is a clean flash or just refreshing /system and /boot. Could you perform a normal clean flash?

Flash Rom, GApps, boot up phone, reboot to recovery, flash my kernel then flash UKM.

Thanks for your patience.
[ONE Original Android Development] DarKAngel1234:
I know it should never be asked, but do you have an ETA on the next Marshmallow Kernel release? This is a pretty slow thread all and all.
[ONE Original Android Development] Renosh:
I've even flashed latest CM12.1 and same issue, can you please consider updating the UKM or the kernel so users of normal CM can use it without issue?
[ONE Original Android Development] RenderBroken:
I am testing the final test build before release. If all goes well I will release tomorrow. Need to test certain things first. Also Yes it has been slow lately, been working my new job, fallout 4 released, and getting close to releasing our new website. So its just been crazy busy, yet I still find time to dev somehow, just not post as much as normal.
[ONE Original Android Development] DarKAngel1234:
Thanks for the update, good luck with the testing. Cheers mate.
[ONE Original Android Development] xflowy:
man. nice to hear. did u include zen decision hotplug?
[ONE Original Android Development] omaralkha99:
u want to game share that fall out 4 with me on ps4 :P
[ONE Original Android Development] RenderBroken:
Not yet, I was looking at it though. Looking at how I could implement it without causing conflicts with my current setup. I think I seen Tyr Kernel had it. I wil most likely pull his stuff in. Why are you so keen on using that particular Hotplug? I am just curious.
[ONE Original Android Development] xflowy:
im currently on lightning kernel with smartmax, zen decision and zen scheduler and its the smoothest thing ive ever experienced. that's why :) and battery life is also great.

would be really nice if u could make it!
[ONE Original Android Development] RenderBroken:
What is your battery life? All Zen HP essentially leaves all cores online while screen is on and then kick them off when screen is off. So with all cores online, I bet performance is smooth. Do you get better batterylife? If so how much and do you have any metrics to back the statement up? I am just looking at this in an analytical way. Because I would love to know.
[ONE Original Android Development] kalapapa:
[MENTION=5438598]RenderBroken[/MENTION]

These are some of my battery stats with Zen and smartmax combo

Please consider adding it

Thanks
[ONE Original Android Development] abhibnl:
With 4 cores online at all times, damn! Those are some stats!

Sent from OnePlus One
[ONE Original Android Development] kalapapa:
That's how I work

I feel like I get better battery with more cores but at lower frequencies rather than one or two at high frequencies
[ONE Original Android Development] kalapapa:
If your not convinced yet look at my stats from today

Just an amazing combo
[ONE Original Android Development] AndreIrawan97:
What is your profile ? :D

Like what's your tweak and your installed apps....
[ONE Original Android Development] FunkyRasta:
Well, there is always a power penalty for hotplugging the cores. That's why zen makes sense. But I just configure bricked hotplug to have two cores always on and have third and fourth hotplug on load above 85 and 95 percent. So they only plugin when they are really needed.
[ONE Original Android Development] xflowy:
[MENTION=5438598]RenderBroken[/MENTION] this.

you can assume that cores going online eats battery life. and that running 4 cores on low freqs is always better than running only 2 on high.
[ONE Original Android Development] RenderBroken:
If we were running a 3.10 based kernel and using heterogeneous multi processing (HMP) Then I would agree that this setup of leaving all 4 cores enabled is a great solution. But our kernel is not really setup to schedule properly for this.

Still, let's continue the debate and testing.

https://drive.google.com/file/d/0B-GVJKBx9-GnVEYyWG02NWIzSlk/view?usp=docslist_api

I have linked a new Test build, the last one, above. It has zen decision for those that want to test, it is not enabled by default though. Also I am testing out a few other changes.
[ONE Original Android Development] KenjiHannya:
Render is one of the best Kernel already tested. I'm testing the Render Kernel-OPO-FC-M-R1-T8-SLEEPSTATES version in ROM darkobas-bacon-20151122-1.

Boot Ok ;D

WiFi Ok ;D
[ONE Original Android Development] KenjiHannya:
As I said... One of the best Kernel already tested and remain.

[MENTION=5438598]RenderBroken[/MENTION] tnx for your hard work

?
[ONE Original Android Development] KenjiHannya:
One more test

Nothing change

30 min = 5% battery used

1 hr = 10 % battery used

Darkobas ROM + Render Kernel = Amazing combo ?

Amazing ?
[ONE Original Android Development] RenderBroken:
So I have had time to play with Zen Decision and I do not believe its actually doing anything. I have messed with its settings so that it doesnt enable cores when battery level is below a certain level and still all 4 cores just stay on all the time. The problem with such is that our Scheduler is not setup to work this way. Also I find that I get the same performance using MSM_Hotplug as I do just enabling all 4 cores on all the time. Barbecue I have MSM_Hotplug set so when you touch the screen, 2 cores are always on at a minimum. When you are reading, it will go down to 1 core. While screen off, it will go down to one core, etc. So I do not believe this other approach to be more energy efficient than my current setup.

Also note that I had tested out Lightning Kernel to see if there was something wrong with my implementation of Zen Decision but his kernel acted the same as mine. I could be wrong in my expectations and may be doing something wrong so if I am please let me know.
[ONE Original Android Development] KenjiHannya:
I believe seeing the results, u made the right choice.

And it did nothing wrong ????

?
[ONE Original Android Development] FunkyRasta:
Also, it is possible to configure bricked hotplug to act as ZEN, apart from the battery related core count (tasker maybe ?). There is built in single core screen off thingy :)
[ONE Original Android Development] _ASSASSIN_:
the point of zen decision was for the Nexus 6 to be close to the stock 5.1.1 kernel which had disabled hotplugging. Zen decision is literally just a thermal driver that turns off cores based on the amount of heat there is, and lets the governor choose how to handle frequencies. However I'd imagine if you run something like hotplug/pegasusq/zzmove or it's variants like nightmare or darkness, it would cause major conflicts. However I do think Mako hotplug is a very interesting hotplug that tries to be different in the way of not trying to imitate MPdecision but rather just has 2 cores for normal interactivity and then 4 cores whenever something intensive runs.

Also the developer who made zen decision has basically left his work so it doesn't get any updates, seems the same way with franco's mako hotplug sadly :(
[ONE Original Android Development] RenderBroken:
Well ppl just get busy. Users do not know how much time goes into development. Still I agree, I know what Zen Decision is supposed to do, what I am saying is its not even doing that. The driver is not working for me nor for lightning kernel. Also on this note, I have already started to port over Mako to see how it will work with my version of cpu-boost instead of his "Touch Boost" setup. Just have to see.
[ONE Original Android Development] SumanthBv:
Does this support fauxsound? If not, add the compatibility please
[ONE Original Android Development] RenderBroken:
Not yet, Faux Sound was causing issues awhile back but i was planning on taking another stab at it for CM13!
[ONE Original Android Development] Luc.Nex:
[MENTION=5438598]RenderBroken[/MENTION] check lightining kernel he implemented some really gr8 audio tweaks http://xdaforums.com/showthread.php?p=63991155#post63991155
[ONE Original Android Development] RenderBroken:
Sounds fun, I will check it out. Thanks js for pointing it out.
[ONE Original Android Development] RenderBroken:
So anyone check out the new site yet? Let me know what you guys think, its been alot of work and I am very proud of the results!

renderserver.net

With this wrapping up, I can start getting back to Developing. I have taken a small break the past week or so. I have a few things I plan on working on in the upcoming releases that I am sure you will be happy about.
[ONE Original Android Development] david72262:
Site looks nice
[ONE Original Android Development] nfin1te:
Any News regarding the final cm12 CAF kernel? *hidesbehindbigrock* :D
[ONE Original Android Development] KenjiHannya:
I had problems with FauxSound Lightning Kernel + Darkobas rom
[ONE Original Android Development] RenderBroken:
well, since moving to the new site I had to wipe my old build environment and now have to set everything back up. I will try to get the final build out in the next couple days.

What kind of issues?
[ONE Original Android Development] KenjiHannya:
Volume is very low, it only returns to normal if you press the button on the handset to meet
[ONE Original Android Development] kouss77550:
Can someone give me a link for render ukm ? The link in the OP doesn't work for me, I guess it's because of the new site ! ;)
[ONE Original Android Development] RenderBroken:
I think you are right lol. Thanks for the heads up!

https://renderserver.net/browse?path=RenderBroken/Render-UKM
[ONE Original Android Development] RenderBroken:
So I have been on hiatus. Working on the awesome new site has been a blast in more ways than one. Its been fun and exciting and also discouraging when others want to bring it down for no reason (DDoS Attacks constantly). Regardless its going strong! Also I have started my new job and have been focusing on it along with the new baby that is about 6 mos old now. So pretty busy. But since I work in education technology, I get the same holidays as the students. Soon I will have a 2 week vacation at my in-laws and will have a metric crap ton of time on my hands. So my plans are to kick everything back into high gear around the 19th. I plan on finally releasing CAF-M-R1 for OPO VERY soon. I have been testing long term and I am VERY happy with the results. I have also been testing up time and memory management and its been freaking phenomenal where I have not had to restart my phone at all. So right now I am about 4 days up time without and lag due to lack of memory and such. This is about the same before I flashed my latest test build. I have been working on LMK and such to manage memory leaks and memory management. Right now, I am happy with what I have done and will most likely not touch it again. lol. It can be very picky. So this coming vacation, I plan on jump starting all my kernel projects and releasing new builds for all. I also plan on releasing the final CM12.1 and CM12.1-CAF builds then too. They have been pretty much ready for release for some time now, just needed to properly finish them up.

Cant wait!

Zachariah
[ONE Original Android Development] KenjiHannya:
Cam wait ?
[ONE Original Android Development] spr33:
Itching to try the new kernel given the LMK changes!
[ONE Original Android Development] RenderBroken:
Hell Yea, it's been awesome. I cannot believe the uptime I am getting. Here is a test build:

https://drive.google.com/file/d/0B-GVJKBx9-GnWkY1MlRwQTVoZ1U/view?usp=docslist_api

Sorry, I am mobile atm. But I have also reworked the workqueue. All round the kernel feels great!
[ONE Original Android Development] spr33:
I'll try it out after the weekend, heading out of town tomorrow. Thanks for letting us test!
[ONE Original Android Development] shubham1120:
Omg thank you so much for this build Zach! Super smooth! Will test battery life for 2-3 charge cycles. Thanks again! On sultan's 11th build.
[ONE Original Android Development] Setting.Out:
Any chances for a non-caf?
[ONE Original Android Development] MBurns2:
yes please :)
[ONE Original Android Development] Spider-Vice:
Amazing quality as always, stable and snappy as hell, however both in this and the earlier test build, I have random SODs and they're so random I can't seem to get a log. Unless there's something I can do after I have to force reboot it?
[ONE Original Android Development] RenderBroken:
Of course!

See above ;)

I will be releasing the final CM12.1 build and will begin work on a new CM13 (Non-CAF) Build soon after. I will most likely follow the footsteps I have made with the new CM13-CAF build.

Have you made any changes from the Stock settings? If so, what are they? What Rom are you using? I am using Sultan's CM13 rom and have had 0 issues with SoDs and I have pretty much tweaked all the settings except for setting the MAX freq while asleep really low and the same for MAX Freq in general. The Lowest I would go is 1.9GHz for MAX Freq. Any extra info you can provide helps greatly! Thanks!
[ONE Original Android Development] Spider-Vice:
Oops, did forget to say which ROM I was on. Sultan's latest 11-12 build. The only thing I have changed from stock is the SELinux permissions, because of Viper4Android. I even deleted Synapse and all its remaining settings from previous kernels. I didn't have random SoD's on another kernel I tested in the same conditions, so not quite sure what may be going on. The issue is they're so random there's not a lot of information I can give you, unless I can grab a kmsg or something after it happens - last time I was literally just using my phone normally, put it on my pocket, when I came back to it and turned it on, only the keys turned on, the screen was dead.

The phone does not stop responding as it vibrates when I long press the power button (to show the power menu). This also happened in the other test build and doesn't happen on Sultan's stock, so it's odd.

Will try to remember to try to grab a kmsg once it happens.
[ONE Original Android Development] RenderBroken:
ok thanks!

So, how many times has this happened since testing the new build I posted today?
[ONE Original Android Development] Spider-Vice:
Only once so far, I was listening to music on my phone though so maybe it's in some specific idle state that it SoD's. It's really odd, it happens so randomly it can either happen in hours from now or immediately.
[ONE Original Android Development] RenderBroken:
Can you tell me the last test build you used that you didn't have an SoD with? If not, Can i setup a folder in my Google Drive that has my Test builds in and you test from Newest to oldest? What you would do is test it til you got an SoD, then test the next oldest and so on. Let me know if that is something you would like to do. I just really want to get this resolved and I too have not idea where to start. Thanks for your help thus far.
[ONE Original Android Development] Spider-Vice:
I'd rather be cutting edge and eventually getting you a log, because I at least only saw two test builds for M from you here in the thread, not sure if I missed any, so I used this one and the one before, which I assume was T8, and both had the issue.
[ONE Original Android Development] KenjiHannya:
Tnx very much mate.

Testing now ?
[ONE Original Android Development] renaltosonylevi:
The T1-R12 kernel seems to work fine with Broken ROM v4.0.

Haven't really had a chance to put it through it's Pace's yet with typical work day use but everything seems stable so far.

But what is really amazing is that the cast of 'American History X' can make ROM at all yet alone one that actually works well.:confused:
[ONE Original Android Development] josera06:
Working fine with slimsaber CAF, very smooth and fast without reboots or fc...

Too early for battery life... But it seems great!!!

Thanks for you work!!

Enviado desde mi Bacon Machine
[ONE Original Android Development] :
Does this kernel works with latest Sultan's 12.1 caf build?
[ONE Original Android Development] KenjiHannya:
Works fine with Darkobas ROM
[ONE Original Android Development] Bobbi lim:
Just to feed my curiosity, that uptime of 4 days you've gotten, what was your SOT? Were you on wifi or data constantly? :laugh:
[ONE Original Android Development] :
I can see a R7 build in the directory https://renderserver.net/browse?path=RenderBroken/OPO/CAF-LP

Going straight from OP gets to home page of renderserver ... Is R7 build is latest build ? Or am I just lost ?