yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
So far so good. Also ported new thermal driver that gives you a bit more options while trying to keep it simple. Its called Bricked Thermal. Also added YankActive. Since i have reworked my cpufreq driver YankActive finally works right and I am really impressed with it. Added Voltage Control as well while I was at it.

R13-T9
[ONE Original Android Development] LiquidSolstice:
Awesome! How is yankactive compared to smartmax? Just as smooth?
[ONE Original Android Development] jduenes:
Awesome thanks for the explanation! Just was hoping I didn't mess something up (:
[ONE Original Android Development] LiquidSolstice:
Hmm, I flashed this, but I don't have any non-standard governers anymore. Not smartmax, not yankactive. Did I mess up?
[ONE Original Android Development] RenderBroken:
Not sure what you did. Try reflecting because I am certain it works for me.
[ONE Original Android Development] Snuzzo:
That's pretty much the same information.
[ONE Original Android Development] schaggo:
Running R13T6, works well so far.

Had a couple reboots, could be tied to my UV though. Still mentioning it, as I ran with more UV before the rebase.

Other than that the usual suspects: freq limits dont stick (prolly due to hotplug or rather cpu-boost messing with the values), a couple gov tunables (yankactive) being read as 0 and once set to a value, once in a while they reset themselves to 0 again.

Logs show nothing. In case I'd capture one, I'd upload it here.
[ONE Original Android Development] Jole7:
I have some new values if you want to try

Deadline:

10 > read_expire

100 > write_expire

8 > writes_starved

0 > front_merges

0 > fifo_batch

2 (all) > nomerge

2 (agressive)> rq_affinity
[ONE Original Android Development] RenderBroken:
Voltagr control may be unstable, I am having to modify the code a but since I am no longer using a major upstream commit that CM did for cpufreq. So thanks for the report I will give it a shot. Also if the reboot was being caused by the scheduler / cpu-boost commits then it would definitely have left something in the log so it a great sign. The rest can be adjusted. Yankactive may need some in or adjustments. Also when you say freq limits don't stick, which? Min, max, or both? Thanks bro.

Sweet thanks! I will try it out.
[ONE Original Android Development] schaggo:
Thanks for the speedy reaction!

Max freq gets reset from time to time from 1958 to 2457. I could not make out any pattern yet. Seems totally random.

As for yankactive, values for (at least, but sometimes some more):

up_threshhold_any_cpu_freq & _load

sync_freq

get set to 0. Some additional get zeroed as well, not this time I checked though. Seems all random...

But working great overall! Fluid, smooth and battery isnt too shabby either, I believe :highfive:
[ONE Original Android Development] meetpatel:
Where can I get cm12s kernel? I read OP twice but can't find,please help.
[ONE Original Android Development] mynameisjon:
Probably going to get hammered for asking, but how do I get the stock color calibration back?
[ONE Original Android Development] _ASSASSIN_:
Literally the same thing as the cm12 kernel.. Not like they use different kernel sources
[ONE Original Android Development] Snuzzo:
Everyone

Please be patient with [MENTION=5438598]RenderBroken[/MENTION] over the course of the upcoming few months. A lot of things are changing in his personal life right now for the better.

Big bro hug to my homey ....
[ONE Original Android Development] schaggo:
[MENTION=5438598]RenderBroken[/MENTION] uuuhm... congrats!? To whatever you are up to or to whatever is up to you, enjoy!

May all your undertakings be of the same excellence as the work you shared here on xda with us! All the best from me, to whatever I may be toasting here! :o

:victory: :good:
[ONE Original Android Development] RenderBroken:
Thanks Shaun!

Yes, my wife and I have welcomed a new baby girl into my family. Lol, first girl in 30 years. I grew up with 3 brothers. . . Really excited guys. My wife and son are too. Thanks guys for the kind words.
[ONE Original Android Development] justimagination:
Congrats to a new addition to the family!!
[ONE Original Android Development] abhibnl:
Congrats for the new princess in your family! I'm sure it'll be a whole new experience for you both than raising a son. Give the love from xda to your new baby girl brother.

Sent from OnePlus One
[ONE Original Android Development] mp3deviant721:
Congrats [MENTION=5438598]RenderBroken[/MENTION]! And good luck with the baby as well!

OnePlus One | Euphoria OS x Metallized edition™
[ONE Original Android Development] wetwhere:
Hi All,

I just wanted to drop a note to say how impressive R13 T3 is. Although I've enjoyed using CM12s I've struggled with battery life and earlier Render Kernels (R6, R10) didn't help. However, R13 T3 seems to work well, is smooth and responsive with default settings, and has excellent battery life.

Thanks again

- WW

---------- Post added at 11:00 PM ---------- Previous post was at 10:30 PM ----------

Hi Again,

Did I miss something or does R13 not have KCAL support?

Also, gratz on the baby, they're as wonderful as they are tiring

Regards,

- WW
[ONE Original Android Development] anhtin:
hi, I am a noob with this kernel. I am currently using CM12s. I installed the kernel but with Synapse, the color profile settings are missing. Please help me.

Thanks
[ONE Original Android Development] RenderBroken:
Yes, with r13, I am still merging major features. I am just stunned that I was able to fix the scheduler "update_task_ravg" rebooting that has plagued this device for some time with the advanced scheduler changes thrown in. It looked to have been caused by sched_clock() giving a negative value when its not allowed. Bow that I know that is resolved I can move on to merging the rest of my feature set.
[ONE Original Android Development] _ASSASSIN_:
Sorry to derail but congrats on the child!

Hope they have just as much patience as you do :)
[ONE Original Android Development] arifqur:
Hearty congrats on the new baby. A boy and a girl, now your family is complete.
[ONE Original Android Development] schaggo:
btw, regarding CAF-based kernel and CM12.1, you might be interested in this, as a proof of concept. dunno if its of any real interest to you though: http://xdaforums.com/oneplus-one/orig-development/rom-kernel-unofficial-cyanogenmod-12-1-t3120259
[ONE Original Android Development] slebit:
Small donation coming your way [MENTION=5438598]RenderBroken[/MENTION]. Confirmation number: 7CM01174T6893954N

And also an update on r13-t9, no problems at all!
[ONE Original Android Development] RenderBroken:
I will only really consider building a kernel for CAF only if more Roms support it. Not really worth doing a complete bringup for a single Rom. I will say that it is something I would like to do though. The Rom and the Dev show lots of promise. Heck I think I even seen myfluxi doing some CAF work for our beloved phone so we may see more CAF Roms like on the Nexus Devices.

Man, thanks for that! Also glad to hear about the test builds performance for you. I am really enthralled that I was able to get past those scheduler random reboots. I am not some super dev that can code really well but I am learning and its cool (to me) to see it pay off. I have been trying to re-learn c++ and other languages as well.

Everyone:

Note that Synapse/UKM will not work right with my kernel. So whatever options there are that are not working, use Kernel Adiutor in the meantime. I am currently using it myself and if it supported some of the more advanced options like MSM_Limiter and such, I would use it full-time.
[ONE Original Android Development] schaggo:
I read that before and obviously didn't understand it the first time round... :eek:

That rom I linked to is therefore not so much a stock CM build with a CAF-based kernel but a (heavily?) adapted CM build, made compatible with the accompanying CAF kernel?
[ONE Original Android Development] Quasar:
I could try and get Grarak to support MSM_limiter etc. on KA. Will keep you posted. ;)
[ONE Original Android Development] RenderBroken:
You are correct. There are alot more changes than just the kernel. But, other roms should be able to use his device trees and such to make their roms CAF as well so I could see more CAF roms in the future.

If you know him personally, let him know I am here for any questions. If he needs the sysfs paths, I can get those too.
[ONE Original Android Development] Quasar:
Will do so, but don't expect any quick implementations. He's one lazy bugger :p. (Don't tell him I said this ;) )
[ONE Original Android Development] sbshunter:
Hi

Can i use this kernel with dirty unicorns v9.4?
[ONE Original Android Development] RenderBroken:
I believe so. It uses CM Device Trees if i remember correctly so it should work with no problems.
[ONE Original Android Development] harpin14789:
I had a boot loop with R11 with Blisspop ROM, but R9 works perfectly well. On the OP, I see changelog for R10 but I cannot find R10 zip anywhere. It goes directly from R9 to R11. Maybe R10 will work without a bootloop for me. Please help
[ONE Original Android Development] RenderBroken:
New build on its way that should have all the issues fixed.
[ONE Original Android Development] slebit:
Awesome!
[ONE Original Android Development] Hiro Nakamura:
Is it fully compatible with your render ukm ?
[ONE Original Android Development] RenderBroken:
I don't know about fully but it should be close if not.
[ONE Original Android Development] gianton:
r13 working great so far with stock settings on [MENTION=2332422]temasek[/MENTION] latest build. Really smooth UI, thanks [MENTION=5438598]RenderBroken[/MENTION] for your hard work.
[ONE Original Android Development] MBurns2:
[MENTION=5438598]RenderBroken[/MENTION] congrats buddy :)
[ONE Original Android Development] SanXacobe:
You've raised the bar again with r13; everything is smooth, as expected. Thanks again for all your hard work.:good:
[ONE Original Android Development] RenderBroken:
Yea, I am really happy with r13 right now. It does seem to be smoother than r9. Also I have been using yankactive. Really impressed with it and I have it tuned to be more battery friendly. This is also why some of the values are "0". With all tests I have been running along with pure user experience, I feel that yankactive is smoother than smartmax while using lower freqs. I am still testing for battery life though do far, all is well. Everything just plain works, no lockups, gps locks (though this is not really kernel side) and just using the phone is problem free and enjoyable. I have merged in almost all major features, I plan on continuing after I hear back about r13.
[ONE Original Android Development] Blodgarm:
I've been using it for about an hour and it's been pretty good, does it work with ukm, or will it bootloop if I try?
[ONE Original Android Development] RenderBroken:
Works just fine with UKM.
[ONE Original Android Development] Blodgarm:
Alrighty thanks
[ONE Original Android Development] Norapapa:
R13 works very smooth and battery friendly with euphoria. Great job
[ONE Original Android Development] Ofthecats:
I'm not getting deep sleep on r13 and slim saber. Im also missing tunables in synapse, but have read its still in early development.

Please let me know what more I can do to help troubleshoot these issues. :D

Edit: I'm getting deep sleep now. It was charging when I reported no deep sleep. I also uninstalled and reinstalled ukm and synapse.

Still missing some variables. Was at first missing minimum cpu freq sliders, but after reinstall of synapse only gpu frequency sliders are missing.
[ONE Original Android Development] Maestropcxp:
Works fantastic with Euphoria 6.2. No bootloops and great battery perfonmance.
[ONE Original Android Development] Flak:
I'm getting soft reboots with R13 stable and DU 9.4. And they aren't generating last kmsg, so I thought I must be losing it. Grabbed a couple different log apps from playstore (syslog and such). On all of them the last kmsg option is greyed out. So I can get you every log other than last_kmsg.

In the meantime I've cleaned flashed back to a different kernel and DU 9.4 (yes, I clean flash for everything).
[ONE Original Android Development] 1ceb0x:
Just to report on R13 - zero (0) problems on latest SlimSaber for 14 hours of uptime. Wifi is rock solid, no random reboots or soft reboots:

My profile:

yankactive

raw 2048 readahead

cpu boost min interval 30 sec

-50 uV

dirty background ratio 10

dirty ratio 50

laptop mode on

swappiness 10%

cache pressure 100%

Battery life seems holding on really well!

Congratulations for another kick ass release, [MENTION=5438598]RenderBroken[/MENTION]

PS - this is my first charge with R13.
[ONE Original Android Development] Ofthecats:
my phone doesnt deep sleep while charging on same rom.

edit: possibly a rom issue

https://jira.cyanogenmod.org/browse/BACON-1694

Edit2: seems to be normal for Android. I guess I was imagining things. Sorry :o
[ONE Original Android Development] MBurns2:
guys i have this problem with r13, any solutions? i'm with the latest slimlp

edit: after reading the thread better, i found that it is "normal" with r13, i can live with it !

I really like r13 configuration, i'm sure that i will have awesome battery life :)
[ONE Original Android Development] Ofthecats:
I had/have this issue. Reinstalling ukm and synapse seemed to fix some of the missing sliders
[ONE Original Android Development] 1ceb0x:
lol.. well.. AFAIK - phone sits at 300 mhz when charging - that's the min CPU speed at the moment. what exactly do you want your phone to do while charging? and how exactly you can see that your phone isn't going into deep sleep?

from my understading - charging draws some power from the socket/usb port - so that needs some power => the phone won't deep sleep like in idle.

UKM errors out due to the changes done by Render in R13 - he will fix it some day :D
[ONE Original Android Development] Nandeh:
Hi!

Testing last R13 with Carbon and the performance is awesome!

Tomorrow I will test the battery life.

Thanks again [MENTION=5438598]RenderBroken[/MENTION] :)
[ONE Original Android Development] schaggo:
I have hardcore soft reboots. Every couple minutes. I am not sure it is attributable to your kernel but to cm instead: http://xdaforums.com/showpost.php?p=61354784&postcount=502

Other than that nothing worth mentioning.
[ONE Original Android Development] RenderBroken:
That's really weird. I have no such issues but I am on the latest euphoria 6/2 build. Also the fact that no one else is really complaining of the same issue leads me to believe that it's something rom side. Still, keep me in the loop if you can about your problem. So are you on official cm right now?
[ONE Original Android Development] gianton:
+1 r13 works great after 4 days with full testing on my vacation (lots of gps apps, photos, videos etc). Everything is smooth on temasek ROM.
[ONE Original Android Development] schaggo:
Yes, always more or less stock CM nightly. I do occasionally flip back and forth, but my reports are always specific to the setup I use at the moment ;)

I'll of course try to make sense of whats going on and update the thread with more information in case I would get some. I just wanted to get the word out there. That's all.
[ONE Original Android Development] wetwhere:
Hi All,

After several days using R13 on otherwise stock CM12s my battery life and performance have been excellent. As good as CM11s was.

My only observation is the phone will occasionally (maybe once a day) become sluggish and unresponsive for 10 to 20 seconds after which time everything returns to normal. Pretty sure its the Android system running full throttle and not the kernel, per se, but it didn't happen before.

On another note, does anyobe know if the touchscreen fixes in the latest CM12s are something we can incorporate into RenderKernel? I haven't looked to see if they're just binaries or kernel modules or what.

Regards,

WW
[ONE Original Android Development] RenderBroken:
Hey, thanks for the kind words!

For the slowdowns you are talking about, can you get me some logs with syslog after it happens?

Also I am in line with cm12.1 which cm12s uses. I have all touch panel fixes incorporated. Are you still having issues?
[ONE Original Android Development] wetwhere:
I have a very sensitive touchscreen which causes me to click links regularly while scrolling. It was like that on CM11s but its worse under CM12s I think. I haven't noticed a change between, say, the stock kernel and R13.

I'll try and get some logs for you when it pauses.

Regards,

WW
[ONE Original Android Development] 1ceb0x:
yeah i get the same display slowdowns when scrolling but it is not related to the touch driver/panel etc...

what i say with slowdowns is - when you scroll in your app drawer (nova here) sometimes the scroll is registered as touch and i open apps when instead i wanted to scroll. I have had this before and it was fine with AK kernel (256 or so i think it was).

Tbh it does not bother me too much, especially since we don't know why it happens and it might only be our setups as I use conservative and I changed lots of values in Synapse.

What I don't understand is - the phone is super smooth when typing or when opening apps, but swiping left - right, seems that it registers as touch most of the times.

Going to play with my values and see if it is something I changed.
[ONE Original Android Development] RenderBroken:
I use an interactive based setup with no such issues. It could be the conservative governor. Let me know what you come up with!
[ONE Original Android Development] wetwhere:
I don't get slowdowns while scrolling. The phenomenon I experience only occurrs occasionally, maybe once per day. I'm using yankactive now as RenderBroken praised it but I've generally used interactive in the past.

-WW
[ONE Original Android Development] TLengert:
I am also missing sliders in Synapse on R13 and am no longer able to overclock.
[ONE Original Android Development] 1ceb0x:
overclock is not possible atm.

i don't even know why you need to overclock........
[ONE Original Android Development] Spider-Vice:
Overclocking is useless as it just raises the temperature enough to start throttling. It gets even worse than stock.
[ONE Original Android Development] TLengert:
I don't need to overclock but I would like to. I enjoy seeing how far I can tweak a device and it is a bit of a letdown when a tweaking feature is removed.

---------- Post added at 04:31 PM ---------- Previous post was at 04:27 PM ----------

Overclocking is not useless as it improves peak performance. I very rarely hit temperatures above 55c so I do not throttle. I don't know why you all hate on me for wanting to overclock. Overclocking does NOT always run at that clock nor does it always throttle up to that speed. As I have stated before, battery life is not an issue for me and I would rather have peak performance over battery life.
[ONE Original Android Development] ponytojas:
R13 and Aospal don't work well together for me =(

ghost touch, imposible to use the phone.

Previous versión had camera issues on this rom too.
[ONE Original Android Development] RenderBroken:
Not sure why, I have not touched anything as far as the camera goes. It's completely stock. As far as ghost touches go, same, I am completely online with cm. If you could, I would love some logs. Thanks for reporting.
[ONE Original Android Development] ponytojas:
For you :p

I hope it can help in anyway

ht

tp://1drv.ms/1Ckd4Bm

P.D: sorry can't attacth anything
[ONE Original Android Development] RenderBroken:
Nothing really of note in the logcat, could you get me a dmesg immediately after you experience some of these issues? Thanks!
[ONE Original Android Development] schaggo:
Lol... not much response :p (I found none at least)

Somehow I find the popping colours a bit distracting lately. What would be the values to modify to get it more stock-like? As recommended I use Kernel Adiutor.
[ONE Original Android Development] RenderBroken:
I am not sure what the stock values should be. I would imagine everything maxed at 256 (Kernel Adiutor) would be it. If others want, I can remove the color changing part from my kernel. Just let me know guys.
[ONE Original Android Development] schaggo:
Looks softer now, but contrast seems still amoled-like high. Cant find the right values though, too many variables to play with... [emoji14]
[ONE Original Android Development] abhi08638:
Set all values to 255 except hue and min

Edit: these are the values for synapse
[ONE Original Android Development] DerRomtester:
Stock values (sry german language)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] schaggo:
Now it looks undersaturated [MENTION=4804871]DerRomtester[/MENTION] but thats probably because I was looking at overblown colours ? Thanks!
[ONE Original Android Development] ponytojas:
The best I could do, theres a lot of pages but I supose no more than the three o four lastest

htt

ps://onedrive.live.com/redir.aspx?cid=7e79d6d0003d4cb4&resid=7E79D6D0003D4CB4!32147&parId=7E79D6D0003D4CB4!107&authkey=!AF2wzZ6wsFwBqFI&ithint=file%2ctxt
[ONE Original Android Development] RenderBroken:
Thanks! I will take a look asap.
[ONE Original Android Development] ponytojas:
I was thinking about, could it be something drivers related?

Every time I flash your kernel, later if I flash any kernel even stock one I have ghost-touch, I need to dirty flash a nightly and then my rom in order to change the kernel or use stock one without problems.
[ONE Original Android Development] ahaq:
[MENTION=5438598]RenderBroken[/MENTION]

R13 running smooth! Did you see this https://forums.oneplus.net/threads/yng1tas2i3-ota-released.316865/

Does it contain newer screen updates or its same?
[ONE Original Android Development] Snuzzo:
Cm12.1 users ONLY. Can you provide a zip from Syslog on your daily use of about 12hrs. I'm going to help look into the reboot issue.
[ONE Original Android Development] RenderBroken:
My kernel is essentially CM12.1 Stock kernel except I have added:

Hotplugs

Governors

Different Thermal

Scheduler Changes

Cpu boost changes

Some IRQ Changes

Really nothing that should cause any tough issues or such. My kernel is pretty inline with CM12.1. I have not changes major drivers, I have not modified anything major at all.

With that said, I dont really think my kernel is the cause. If so it would happen to more ppl. Also Once you flash AK over my kernel or any other kernel over my own, IT completely overwrites my own and they have clean up scripts that remove my one and only script I use. I tried to keep things simple so other Devs could easily account for it when flashing their own. So I want to say that this is placebo BUT I also believe in Murphy's law and that anything that can go wrong, will go wrong. So I am not writing this off completely because I would love to find the cause. But in my opinion, I do not feel that this is an issue tied to my kernel. Still post in this thread if you find anything out or have more info.

It contains the same commits that are in my own kernel already. Thanks though!
[ONE Original Android Development] RenderBroken:
No one is having reboots in R13. There is a user (ponytojas) having some weird touchscreen issues though. If you can look through the logs he post a couple post back and see if you see anything. I am going to look to but then we can put our heads together in chat.
[ONE Original Android Development] ponytojas:
Maybe it's not kernel related but it's really weird, and believe me, is not placebo, my phone become completly crazy.

I have the same issue with AK kernel, and desapear with the new touch drivers CM merge, for this reason mention it.

Well being more exactly I suffer this issue with some kernel and with some others no.

Maybe is a issue with my device but I say, some kernel make me have it and some kernel not.

Anyway Render, thanks a lot, you're doing an awesome work with the opo as you did with G2, and really I appreciate you've read the logs and you've tried to fix it or at least identify the error