yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
Yes, its incoming.

Have fun!

It is really a good habit to go ahead and flash the rom and everything BUT the kernel. Then make a backup of the BOOT Partition. Then flash the kernel (AK, Render, Tyr, EGG, ETC) This way its always easy to recover or flash another kernel cleanly.
[ONE Original Android Development] UltraBoykj:
Thought I would give this kernel a try however it wouldn't even boot up.

Full f2fs support on all partitions with CAF?

N/M - Search found what I was looking for. Not that I didnt search before, I had just questioned here before I had read them all.
[ONE Original Android Development] RenderBroken:
I believe it is enabled for all partitions. Just make sure to not inject boot image for multirom. That will cause it to not boot too.
[ONE Original Android Development] 3ncrypt3d_Droid:
[MENTION=5438598]RenderBroken[/MENTION]..Yeah, now I see how you build these badass Kernels!! :)
[ONE Original Android Development] RenderBroken:
The penguins are a trade secrete bro. . . Not cool yo
[ONE Original Android Development] 3ncrypt3d_Droid:
Secret is safe with me bro.. No worries..
[ONE Original Android Development] otonieru:
Am still figuring out the fast charging compatibility in this kernel,

i found out that on some chargers & cables, the fast chasrge is working, while with others, it didn't

Example :

with Xiaomi 2.0A Charger it refuses to go beyond 400mA, but when the charger plugged to other phone (Moto X, Mi Note Pro & Andromax) it charge rapidly at around 1200-1300mA level

with Apple 1.0A Charger, it charge well at 700mA level

with Hippo Dynamic 2.1 A Charger it also charge well at 900mA level, but then

with LONIO 3.0A Charger, it refuses to go beyond 400mA as well, while other phone do well with the charger

and with OPPO VOOC Charger, it only give around 600mA, while when plugged to other phones, it surpass 1000mA

same case happen if i swap between one cable with another (all cables work normal on other phones, but slow with OPO)

quite weird don't you think?
[ONE Original Android Development] Ofthecats:
Is the screen on when you check?
[ONE Original Android Development] omaralkha99:
flashed the kernel on sultanxda caf f2fs rom, and tried tweaking it using synapse app, but when I open it I get this messege "no UCL support detected", did I do anything wrong, or anything I need to do first?
[ONE Original Android Development] Setting.Out:
Flash UKM..
[ONE Original Android Development] omaralkha99:
sorry tottaly forgot about that, tnx

---------- Post added 15th October 2015 at 12:06 AM ---------- Previous post was 14th October 2015 at 11:44 PM ----------

tried flashing kernel and ukm on temasek rom, getting bootloop. f2fs and no caf (tried not caf kernel varient), any ideas?
[ONE Original Android Development] Setting.Out:
Problems with f2fs..
[ONE Original Android Development] omaralkha99:
tnx, would u think going back to ext4 is worth it for the kernel, or just flash a kernel that supports f2fs?
[ONE Original Android Development] _ASSASSIN_:
it's kind of pointless just to loose all of your data for a kernel IMO. But you do you.

Probably the best kernel alternative would be AK
[ONE Original Android Development] Setting.Out:
You are limited on f2fs and see very minimal gains on tests, but not in how it feels.. Regardless of kernel, I'd switch back to ext4..
[ONE Original Android Development] RenderBroken:
I am very close to release. I have been getting a weird bug with Bluetooth headsets. Whats happening is the phone would randomly lockup and reboot. Can anyone else confirm this? This is happening with my CAF kernel. If it happens to you, please get me some logs. Thanks!
[ONE Original Android Development] nfin1te:
Im on CAF euphoria with your kernel, using AKG Y55 BTs.... no such issue here.
[ONE Original Android Development] Blodgarm:
No issues so far with bt headsets, using my lg tone pro's
[ONE Original Android Development] erad1:
Could anyone direct me to the correct .defconfig to compile a build. I forked recent source and and older branch. So far not having much luck with trying to compile older builds that use prima drivers (needed). Not sure but it may be my build environment. Getting errors like files not found and stuff. Any help at all will be appreciated.
[ONE Original Android Development] jukiewalsh:
Which repo? I think you're looking for Arch/arm/configs/render_defconfig

And do you have ccache installed?
[ONE Original Android Development] erad1:
This repo; https://github.com/THERAD1/OPO-CAF-kernel and not sure if ccache as I followed a tutorial on installing the build environment itself. I really want to compile a build from July/August as they are supposed to have needed wireless driver functionality needed. Thanks in advance if you got anything to advise. :good:
[ONE Original Android Development] RenderBroken:
What exactly are you aiming to do? Let me know and I may assist.
[ONE Original Android Development] erad1:
I was trying to compile/make your kernel compatible with AOSParadox 5.1.1, I'm sure you're already aware that everything works fine but it breaks wifi. Totally noob effort on my part but was unsuccessfull. :silly:
[ONE Original Android Development] RenderBroken:
I will take a look and see what I can do. Most likely I can make my kernel compatible. I think know he is just using prima drivers.
[ONE Original Android Development] kalapapa:
[MENTION=5438598]RenderBroken[/MENTION]

Apparently they're gonna release a marshmallow build either today or tomorrow so I would wait until then
[ONE Original Android Development] erad1:
Thanks was meant for [MENTION=5438598]RenderBroken[/MENTION] sorry, the MM build is already going to be compatible. (see changes here).

It would be greatly appreciated if you did! The AOSParadox devs re-wrote some code for the new base, but a compatible RenderBroken kernel for the 5.1.1 build would still be very welcome by many! A lot of users will not be looking to jump to MM right away.
[ONE Original Android Development] RenderBroken:
I believe I have finally been able to fix my personal bluetooth issues! YEA! So I am doing some last minute testing and should be releasing a new build today!
[ONE Original Android Development] [armitage]:
Sorry couldn't resist. :P

Really love your kernel. Thanks for the great work.
[ONE Original Android Development] spr33:
Saw that the new build was up, downloaded but awaiting changelog :)
[ONE Original Android Development] Formhault:
He probably fell asleep on the desk :)
[ONE Original Android Development] Setting.Out:
He needs a new computer... ;)
[ONE Original Android Development] RenderBroken:
Thanks! I am trying! I had the "Problem finally comes back as you are thinking you are done" problem. But I am tracking it down. It happens even with R7, R6, R5, and R4. I am testing it with R3. I am trying to narrow down the exact cause and becasue most of my releases are not just a couple commits each, it makes it a little harder.

Yea, maybe having my computer on the side of my bed was not a very good, productive idea.

LOL. I would never release if that was the case. . .

pillow. . case. . .nvm
[ONE Original Android Development] erad1:
...new release? Was it pulled? it's still R7 Sept 15 for CAF build.
[ONE Original Android Development] madsponge26:
Not yet mate.. Im still excited to test the new kernel..
[ONE Original Android Development] 15H44N:
So.. Can you Roll out a build for COS12.1 YOG4PAS1N0 ?

Or is it already present?

Please... I'm dying to use this kernel
[ONE Original Android Development] RenderBroken:
Yes, my CM Kernel should work just fine with that build.

Also as things like this normally go. (Not really, just an OCD Dev) I am working on a new branch for my kernel. I am working on doing some cleanup. I am looking at making some pretty big "under the hood" changes. Just fyi.
[ONE Original Android Development] xflowy:
hey im coming from ak kernel. can someone tell me what to do with the ukm zip from here? do i need to flash this prior to the kernel flashing? thanks!
[ONE Original Android Development] Formhault:
If you want to use Synapse, you must flash it (after you flash the kernel).
[ONE Original Android Development] xflowy:
thanks. and if i only wanna use kernel adiutor im good without ukm?
[ONE Original Android Development] RenderBroken:
Here we go!

I have a test build for yall to try out and report back your experience. One thing I am going to say is its realllllllllllly smooth. With that said i am curious about battery life. But it is performing like I expect. There are certain things I look for when judging how well it will do with battery life and it has meet those expectations. But you be the judge.

R8-T17 Download
[ONE Original Android Development] madsponge26:
Yes! Time to shine!

This is caf?
[ONE Original Android Development] xflowy:
caf?

aaand: is scheduler tripndroid included?
[ONE Original Android Development] madsponge26:
Yes! Caf kernel..

[IMG="caf kernel"]http://i1031.photobucket.com/albums/y377/madsponge26/Screenshot_2015-10-25-19-14-33_zpsw5zpi4ul.png[/IMG]
[ONE Original Android Development] [armitage]:
RenderKernel-OPO-CAF-R8-T17
[ONE Original Android Development] madsponge26:
Yup. Its already mentioned. Im gonna test the battery juice.
[ONE Original Android Development] RenderBroken:
Thanks for testing guys, I have noticed some random reboots caused by watchdog bites. I believe it is caused by SELinux flooding logs. I will have to diagnose this further but in the meantime, use an app like kernel aduitor and use the plug in feature, or use synapse to set SELinux to not enforcing.
[ONE Original Android Development] spr33:
Flashed just and within 5 minutes I had a RR ;(
[ONE Original Android Development] Ofthecats:
Please see if you can share your lastkmsg [MENTION=396391]spr33[/MENTION]
[ONE Original Android Development] spr33:
I'll share next time it happens :) I've just set SELinux to permissive so hopefully it won't happen again.
[ONE Original Android Development] erad1:
just curious...any chance this build is AOSParadox compatible?
[ONE Original Android Development] RenderBroken:
Highly doubt it. I am not going to waste time building for a single rom atm. If it became more popular then I can see it but I would much rather build using a standard source.
[ONE Original Android Development] _ASSASSIN_:
only difference was the PRIMA driver I'm pretty sure, not that big of a change. Even so you have to deal with the problems with that.
[ONE Original Android Development] erad1:
OK. Thanks
[ONE Original Android Development] joefso:
There is already an rom that uses render kernel in combination with AOSParadox, it is called radonX, soon they will update to M. It is probably easy to do yourself or extract and flash it
[ONE Original Android Development] RenderBroken:
You are right. Sorry, I have too much going on and its hard to keep up with everything lol. I was actually planning on trying something different like building WiFi as a module and when flashing my kernel, it installs the proper WiFi Module depending on Rom Version. Just an idea but with my AnyKernel, anything is possible.
[ONE Original Android Development] xflowy:
is r6 the newest stable caf, cause it says so in the thread title. but r7 is also available.
[ONE Original Android Development] [armitage]:
Ok. this didn't go too well. Flashed the (r8 test) kernel last night and as it was already pretty late and I couldn't test too much, so I put the phone, at 100% battery, in airplane mode (as I always do at night) and this morning when I woke up the screen was black, the phone completely frozen, so that I had to force a reboot and the battery dropped from 100% to 27% (with the last kernel it dropped 0-2% max.). Like I said... It didn't go too well, so far. :D

Ps. Same just happened again. Just left it, with screen off, for a couple minutes and it became completely unresponsive again and I had to force a reboot. Sorry, I love to test stuff, but I have to go to work soon and I need a reliable phone, so I can't test this kernel any further.
[ONE Original Android Development] xflowy:
I guess you are talking about the r8 test build posted some pages ago.

As you refered to me, I'll just leave this there. I was asking about r6/r7.

though I can confirm your issues with the r8 test build!
[ONE Original Android Development] [armitage]:
Of course you're right.I clicked the wrong button when I posted the reply. Thanks for clearing that up.

Edit: Fixed the post. :)
[ONE Original Android Development] xflowy:
do u guys rather use msm or msm mpdecision hotplug? which one is smoother?
[ONE Original Android Development] LittleConfucy:
Render kernel and XenonHD

Has anyone got this kernel to work with the latest XenonHD CAF weekly? Last time I tried, System UI crashed... :(
[ONE Original Android Development] xflowy:
how is r8 (i reckon a test build was already on here) doing? :)
[ONE Original Android Development] RenderBroken:
Been going great. I have been working like crazy on the personal Random Reboot issue I have been having while using my plantronic bluetooth. Very weird issue but I think I am getting to the bottom of it. regardless. I have some cool things in R8 coming out.
[ONE Original Android Development] Promez:
Are you working only on CAF version or will be also a CM version? :D
[ONE Original Android Development] xflowy:
good to hear man! keep it up. looking forward to it.

are u talking about blackening screen or even reboots when listening to music over bluetooth? cause thats what im experiencing with ak kernel.
[ONE Original Android Development] RenderBroken:
Not really. The issue is that I get soft reboots. Also Only I have this issue. not one else with BT Headsets have such a problem and I believe it has to do with my headset being mono.
[ONE Original Android Development] xflowy:
79X42404J31135907

little donation as appreciation and to keep you motivated ;)
[ONE Original Android Development] RenderBroken:
Well thanks! It's always appreciated.

Yea I have been testing my ass off for r8. Right now I am testing build 31. Lol.
[ONE Original Android Development] vjsanjay:
Can you upload build 31 for testing
[ONE Original Android Development] RenderBroken:
Have fun:

https://drive.google.com/file/d/0B-GVJKBx9-GnUWlqUlRpV3BGczQ/view?usp=docslist_api
[ONE Original Android Development] dolbylogic:
This thing is running Silky Smooth...
[ONE Original Android Development] vjsanjay:
Very smooth... So far no issues.
[ONE Original Android Development] beaverhead:
very smooth and no reboots.so far so good.
[ONE Original Android Development] molonad:
So on your latest version is speaker doesnt working? Other side cant hear me? :eek: or i Dont understand it well?
[ONE Original Android Development] gianton:
Read previous page has been reported already, dev is working on it.
[ONE Original Android Development] molonad:
Yes i Red all of it, but i didn't understand it well, so I must switch to ak ? for now, but i just tried kernel now it is awesome!!
[ONE Original Android Development] gianton:
If it's an important feature for you, you'd have to use another kernel.
[ONE Original Android Development] molonad:
I tried this kernel, great festures, this is exactly what i was looking for, only think i notice is bugged msm mpdecision hotplug, when I touch backup current profile all cpus are boosted and Dont unplugg, and sometimes when i was changing something in hotplug all freeze and i must restart phone, so only this and speaker is problem for me, if it is fixed i Will be very satisfied with this kernel
[ONE Original Android Development] RenderBroken:
Weird, u have bit experienced this yet but will try to trigger is. Any other info you can provide would be appreciated.
[ONE Original Android Development] molonad:
Lets try yourself, just click MSM MPDecision 1 core min 4 cores max and backup your profile and then click restart and check how are your cores working, all of them will be plugged even if you do nothing. Dont know if it si conected with my each core governor or every core min Max frequency, if you want i can record it and post Link
[ONE Original Android Development] RenderBroken:
I will give it a shot. Thanks for the steps.
[ONE Original Android Development] molonad:
Hey, thanx for your kernel, each core frequency and governor is exactly what i missed, iam supporting you in your work thanx ☺
[ONE Original Android Development] ahaq:
When will you be pushing out mic fix and speaker
[ONE Original Android Development] RenderBroken:
Not sure about mic, I have a few ideas about what the possible problem may be. But what about the speaker? I don't remember any complaints about that.
[ONE Original Android Development] ahaq:
Sorry sorry I mean mic when in speaker phone while talking other person can't hear
[ONE Original Android Development] endriuss:
Maybe I misunderstood something but just a while before I've made 2 test calls. I turned on the speaker during the call and the other person can hear me very well.

Sorry if this is not the problem you are talking about. I'm on the R3 T1.
[ONE Original Android Development] clockworkstop:
Well, I do have a complaint about the speaker. The volume is all jacked up with your kernel, but using AK fixes it.
[ONE Original Android Development] RenderBroken:
No problem, thanks for clarifying.

An update on what I have done today. . .

I have done massive reworking of scheduler and cpu boost. At the moment cpu-boost is pretty dumb but now it actually accounts for workload. But with this setup, there were alot of random reboots so Steve (Cyanogenmod) had reverted these squashed commits. While I was digging through code making sure the cpu-boost changes I had made, I noticed some code that may be tied to the reboots that was missing in cpu-boost. I was referencing my G2 kernel where I have all of this working properly and noticed that there were code that I had in my G2 kernel that was not in my OPO kernel so I have to reset the cpu-boost driver back pretty far to then re-commit my changes on top in the correct order. Now, I am not sure if this will fix the problem but so far so good with my personal test build I am running. I will continue into tomorrow and if all is well, I will release R3 with these changes. I will say that the performance gain is awesome and near stock kernel. The Stock kernel seems to run very fluid but that is due to the stock Hotplug driver being overzealous meaning that if you looked at how many cores are online, you will see wither 3 or 4 cores online to produce the smoothness that you see. Well I want to do the same performance with just 2 cores. So if I can get the same performance and then some along with better battery life, I am happy and am achieving my goal.
[ONE Original Android Development] RenderBroken:
Can I get more info about it being jacked up? AK uses the same sound driver I do. But maybe more information will make more sense.
[ONE Original Android Development] gianton:
This issue is confirmed by the dev too, so it's definitely there. Hopefully will be fixed soon.
[ONE Original Android Development] clockworkstop:
The sound is very loud even if the volume is low and turned up only one step and when I play any music, the highs and lows and mids are very imbalanced. The singing periodically gets louder and the quality is also very poor. The same happens when listening with headphones.

After flashing another kernel all was fine, I just flashed your kernel and it happened again.

I don't know what other information to give you though, sorry.
[ONE Original Android Development] ahaq:
This gonna be awesome! Your dedication and effort, amazing!
[ONE Original Android Development] ak:
I'm using the first implementation ... And it working without problems ... [emoji6]

Sent from my A0001
[ONE Original Android Development] xflowy:
any chance to get zzmoove governor implemented?
[ONE Original Android Development] RenderBroken:
I thought it already was. I will take a look. I am still having BT issues though. . .
[ONE Original Android Development] beaverhead:
zzmoove is implemented.
[ONE Original Android Development] amardeep434:
Which version should i flash for cos 12.1 YOG4PAS2QL ?
[ONE Original Android Development] xflowy:
guys, my bad. i meant zzmoove HOTPLUG, not the gov :D
[ONE Original Android Development] kalapapa:
Yah that would be awesome
[ONE Original Android Development] DerRomtester:
There is no zzmove hotplug. The hotplugging mechanic is integrated in the CPU governor called zzmoove.
[ONE Original Android Development] xflowy:
on boeffla you can choose zzmoove hotplug! so how's that?
[ONE Original Android Development] kalapapa:
This is true but the issue is that in synapse you can't edit the specific hotplug tunables

The only way to do it is through kernel adiutor
[ONE Original Android Development] DerRomtester:
This is the way how the Lord implemeted it to his app but the CPU governor is actually doing this job if you know the code. Go to the Lords kernel git and browse to the folder drivers/cpufreq/cpufreq_zzmoove

APP = not the truth :)

Than open that file and search for hotplug. I am sure you will some lines called hotplug vor sth like that.

This is the way how the apps handle this. :)
[ONE Original Android Development] Snuzzo:
Can I get one or two testers. Pm me please.
[ONE Original Android Development] RenderBroken:
Really more info would be helpful to the users. Right now Plain Andy is doing some testing on my behalf. He is testing some experimental changes based on my own source so if you are interested in testing new Render Builds, get with Plain.

Thanks guys!
[ONE Original Android Development] RenderBroken:
So things have been slow for me, just been busy as hell. New Site, new job, new baby, etc. LEts of new and FA4 out tomorrow?! I will never get anything done. . .lol jk

I have been testing a new CM13-CAF build. Been running fantastic. I am testing to see if my own personal Hell Bug is still present. I was still getting Random Reboots with R7 - R1. Its been hard to pin point but with my new test build I have made some small changes that I believe should help my issue. I could have released R8 a long time ago but when there is something like this, it drives me nuts and I want to fix it before release. Regardless, working on rebase for CM12-CAF and CM13-CAF. Not sure if I will continue working on LP-CAF or if I will just move on. We will see if there is much need for it. I always like to move forward.
[ONE Original Android Development] Nandeh:
Great news! Can't wait to test your CAF CM13 kernel mate!

I'm with Sultan CAF CM13 ROM and it works really fine, and I'm sure that with your kernel it will fly.

Thanks!!

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] xflowy:
any chance to get the r8 for 12.1 build out these days? :)
[ONE Original Android Development] RenderBroken:
Yes, I will just go ahead and release what I have so far. Just have to find time to finalize and release. Fallout 4 is making that hard along with my two jobs lol.
[ONE Original Android Development] xflowy:
niceee
[ONE Original Android Development] RenderBroken:
Cuz I like to share:

R1-T1 for CM13-CAF is here!

Download

This is just a test build. So far for me, It outperforms the stock kernel in every way. Better performance and battery. Let me know if you guys have the same experience!

Also note, alot will be missing as I am starting from scratch again to remove extra cruft.
[ONE Original Android Development] kalapapa:
Thanks [emoji4]
[ONE Original Android Development] xflowy:
and r8 for cm 12.1? :)

also: would u mind adding zen decision hotplug to your kernel?
[ONE Original Android Development] shield1331:
Rom didnt boot on c13 caf sultan 13/11 build with ur test kernel
[ONE Original Android Development] Hiro Nakamura:
I am having quite a bit of Wlan battery drain with this kernel
[ONE Original Android Development] RenderBroken:
Most likely just need to update. Thanks for the heads up.

Same here. I am always inline with Sultan so Wifi should be the same but he reverted back a recent change that I need to make as well.
[ONE Original Android Development] Hiro Nakamura:
Cool, can you upload the one with the old wifi drivers please?
[ONE Original Android Development] Formhault:
Wi-Fi drains battery on Android M. It's a Google thing...