yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
I realized I did not have MultiRom support added back in when I was working through rebasing my kernel, and fixing issues with the initial bringup. It will be in R2 for sure.
[ONE Original Android Development] Beaster:
I just flashed your kernel on top of CM12 nightly.

Will report if something goes wrong! So far all is looking good!

Thank you for your work!
[ONE Original Android Development] smoki3:
T9 is running great. Thanks
[ONE Original Android Development] S1ay3r666:
T9 kernel is running perfect with Euphoria Os! Great Job
[ONE Original Android Development] RenderBroken:
I have to agree. I just started using Euphoria and I am blown away. This is the smoothest android experience I have ever had.
[ONE Original Android Development] Thunderbolt:
I had autoreboot 5 minutes after install this kernel On euphoria.
[ONE Original Android Development] sneakerspark:
RenderBroken is using that ROM himself with this kernal. I guess he never encountered such issue. Were u using synapse with the previous kernel you had? Maybe the particular profile for the previous kernel is conflicting with this kernel.

Sent from my Oneplus One
[ONE Original Android Development] schaggo:
I know its OT but it bothers me so much when someone refuses to pay attention on how k-e-r-n-e-l is spellt, I just have to type this message. Cannot resist in my current mood.

http://en.m.wikipedia.org/wiki/Kernel_(operating_system)
[ONE Original Android Development] Thunderbolt:
I didnt use synapse On this kernel. Just Flashed. Next reboot after received SMS.
[ONE Original Android Development] RenderBroken:
You must not be using may latest test version along with using Ambient Display. There is an issue with R1 and Ambient Display. So either go look the past couple pages for my new test version or don't use Ambient Display til R2 is released, which is soon ;)
[ONE Original Android Development] Thunderbolt:
So should I Flash r2 version?
[ONE Original Android Development] Beaster:
Either flash the test kernel quoted above or wait for R2 once it is released.

Personally i ve been running the test build and have been rock solid.

Eagerly waiting for R2!
[ONE Original Android Development] Az-one786:
Blazing fast on Cyanhakers also .... But I'm still on T5 ... will test T9 now ....

Thanks ....
[ONE Original Android Development] varund7726:
Nice to see you here too [MENTION=5438598]RenderBroken[/MENTION] :)

keep up the good work
[ONE Original Android Development] frickinjerms:
So I hopped off blisspop and tyr kernel after a month of using them and looked to see what other fun there was, so I clean flashed euphoria os and the second test build as people here had said it was legit, and geez Louise it's a fabulous combo! Excellent excellent excellent!
[ONE Original Android Development] schaggo:
OMG OMG OMG OMG!!!11!!one!!11one11eleven!!

Please for the love of god tell me how to get that overlay with core frequency! Been looking for it for months...!
[ONE Original Android Development] abhi08638:
It's a rom feature that you can find under developer options called show cpu info. However not all roms have it, I know blisspop and slim saber do
[ONE Original Android Development] schaggo:
Unfortunately CM does not :( They only show the default overlay which comes with AOSP. Thanks for answering.

Had bootloops again with R11 following a regular reboot. I will flash the test builds, give them a couple hours and report back any interesting findings.
[ONE Original Android Development] mp3deviant721:
Euphoria has it. I just wish I could change the color of it...

OnePlus One | Powered by EuphoriaOS x RenderKernel
[ONE Original Android Development] RenderBroken:
I would always consider any feature request.

Free app from the Play Store called Cool Tool

With it you can create your own overlay, color it, add graphs, move it around to any locations etc. I use it for debugging. It does have a slight learning curve but nothing I am sure you could not figure out. Also if there is an option that you want but don't see, you can create your own. For example when I was testing GPU OC I needed to watch the GPU freq during tests but the program didn't have the option that covered it. So I just created one where you just use the sysfs path that would give you the info and place it in the program were it says, Name it, then it worked fine after that.
[ONE Original Android Development] _ASSASSIN_:
you can use this. Same thing just not native

http://xdaforums.com/showthread.php?t=1933284
[ONE Original Android Development] mp3deviant721:
I only ask because some devs don't like asking for feature requests. Anyway....

How about the Lionheart governor? Its probably the snappiest governor I've used on this device. Period.

OnePlus One | Powered by EuphoriaOS x RenderKernel
[ONE Original Android Development] schaggo:
CM12.1 nightly from 3.6. (yesterday). Both loop.

Procedure: Flash UKM unintaller. Then wipe /system, flash ROM, kernel, RenderUKM.

Btw, both kernel boot when powered off and left for dead for a couple minutes.

---------- Post added at 15:36 ---------- Previous post was at 15:30 ----------

Had a look at it a couple weeks ago. Too dumb to use it obviously, I did not arrive in successfully displaying core state & freq for my governor tunable testing activities.

I'll have a look at tool cool again first and if I fail again, I'll probably take that. Used trepn profiler but that one is quite heavy itself and skews the picture. Inaccurate measurements.
[ONE Original Android Development] RenderBroken:
I will take a look and maybe run a test build with it. One I do plan on giving a shot in the near future is DanceDance created by [MENTION=3419683]Snuzzo[/MENTION] I have been wanting to try that one for awhile and he is going to give me a hand in making sure I can get it in its best form yet.

Next build will have both reverted at the same time. Thanks for letting me know!
[ONE Original Android Development] Snuzzo:
Will be fairly simple to get going. Hit me up on 'Outs whenever...
[ONE Original Android Development] RenderBroken:
New test build:

R12-T4

This has booth commits reverted. Please let me know so I can proceed and do another test build if needed.
[ONE Original Android Development] _ASSASSIN_:
Eh, I still think performance is by far the fastest governor out there :P

Lionheart is OK but if you want something similar go with slim TBH. Lionheart is based on conservative so it uses conservative logic which means it won't be as responsive as a interactive based governor like slim is. (if you desire snappiness)

Slim governor is basically just the elementalx governor.

I'm more interested in seeing interactiveX or interactive governors with more exposed tunables to tweak in synapse :)
[ONE Original Android Development] frickinjerms:
R12-T4 bootpooped me on the 1+ splash zzt zzzt, didn't even make it to the euphoria boot animation, reflashed R11-T3 and booted up without issue like before
[ONE Original Android Development] dude6595:
T4 booted for me on latest euphoria.... Flashed over T3 which also works for me...
[ONE Original Android Development] LiquidSolstice:
Flashed over R12 on Euphoria (Jun02), looped once, and booted properly the on second loop. I think you're on to something!
[ONE Original Android Development] mp3deviant721:
You are technically correct about performance. Lol

Lionheart just feels snappy to me though. And according to this:

http://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957

It is more of a performance orientated governor... At least that's what that guy says...

OnePlus One | Powered by EuphoriaOS x RenderKernel
[ONE Original Android Development] Norapapa:
Its so crazy. My running system yesterday was euphoria 2.6. + R12T3. Go to recovery an make a backup. Than i flash R12T4 and i have a bootloop. I go to recovery and flash R12T3 and i have a bootloop. I go to recovery and restore the nandroid backup (euphoria+R12T3) and i have a bootloop. I go to recovery and restore the nandroid backup with the euphoria with stock kernel and my opo Boot normal.
[ONE Original Android Development] schaggo:
R12T4 booted ok this morning. Same setup as yesterday, same procedure: wipe /system, flash UKM uninstaller, flash CM12.1 03.06. nightly build, flash kernel and RenderUKM. Then the addons, then reboot straight out of recovery.

I will wipe and flash again, for the sake of the experiment.

Update: Made a second go-around and this time it looped. Exact same setup and procedure as always.

Update: Made a third go-around. This time it rebooted once after the bootloader screen completed and then came up.

Update2: I seem to fail to find out, how exactly UKM&Synapse works. Up until now, I figured Synapse writes certain values into init.d scripts (or similar) which then get applied during bootup.

After some research just now, I believe this is not true. Synapse sets the values similar/identical to other kernel tuning tools upon a completed boot and UKM is the a way to get the tunables into Synapse. The parameters you set in Synapse do not get applied during boot but similar to other tools, after boot. Is that correct?
[ONE Original Android Development] jduenes:
They only kernel that doesn't give me problems is R9, everything beyond that puts my phone in bootloop sadly I am on cm12s
[ONE Original Android Development] RenderBroken:
Well guys, not sure the exact issue. The problem for me is the new commits that are mysteriously causing the issue should JUST WORK. I shouldn't have to revert anything and that makes me wonder what exactly isn't playing nicely. Finding what that is, is a whole other story. Not sure if I should just work on the rebase in the meantime. Not sure if I even want to keep spinning my wheels on something that doesn't make the least bit of sense. I am someone who hates standing still and I feel like that's what I am doing. So with that, I plan on just working on a new rebase. Doing some house cleaning. Working on some new code that I want to base on top of but have to see how it goes. Thanks guys for your patience..
[ONE Original Android Development] HaTrED_:
It's kinda weird, or very very strange, when "similar" systems under same kernel versions and ROM's, shows us different behaviors - one guy gets a boot loop, others don't!

I've been reading this all debate and doing some testing and it seems to be just very random! I'm not able to establish a coherent correlation cause versus effect! So, under this conditions, it's perfectly understandable your "frustration" but let's hope that this new rebase brings us something new!

Keep up the good work mate! All your efforts will bring great results! :p
[ONE Original Android Development] dolbylogic:
[MENTION=5438598]RenderBroken[/MENTION] don't give up and thank you for your hard work.. Bootloops or not you have been great. Keep up the good work....
[ONE Original Android Development] Snuzzo:
[MENTION=5438598]RenderBroken[/MENTION]

Woke up this morning to my favorite cereal expecting Cocoa Puffs I got these instead ....

... Just kidding lol

I'm certain between us we can get the 'loops resolved.
[ONE Original Android Development] RenderBroken:
That was a good laugh! Thanks Snuzz!
[ONE Original Android Development] RenderBroken:
I think the rebase will be a good thing. There were some things merged in from CM (Upstream stuff) that I have been wanting to revert and redo. I am finally going to bite the bullet and do it.
[ONE Original Android Development] jduenes:
Well man, whatever works. Your kernel is my favorite kernel. Even though this is happening, i refuse to switch to anything else lol. Keep up the good work man (:
[ONE Original Android Development] RenderBroken:
Thanks!!

I plan on releasing a new test build tonight that is the beginning of the new rebase. I may add the hotplug drivers and I might not. Main thing is the new scheduler changes and cpu-boost rework. I will also leave mpdecision (Stock QCOM Hotplug) alone in future builds but just have it disabled. Some like to use it and I have been able to remove the input boost ability of it to make it use cpu-boost instead and not step on each other's toes.

Also if you want to keep up with what I am doing look here:

https://github.com/RenderBroken/msm8974_OPO_render_kernel/commits/rebase
[ONE Original Android Development] mp3deviant721:
Can't wait to test the new rebase! I went back to my previous kernel because I was having gesture wake lag and screen off gesture unresponsiveness no matter what governor I used...

OnePlus One | EuphoriaOS x Boeffla edition™
[ONE Original Android Development] _ASSASSIN_:
rebasing from CAF or from the stock cyanogen kernel?

CAF has a lot to offer in terms of performance versus the stock cyanogen kernels, you should look into it ;)

also misc. comment, but I just want to say that I've had so many issues with many kernels with having re-draws with so many apps. Using VFS pressure and swappiness at 10% makes it so that the phone actually uses the 3 gigs that it has of RAM and also has no redraws from my experience. Could try it out on the rebase :D
[ONE Original Android Development] _ASSASSIN_:
Boots with latest slimsaber.

Disabled msm limiter and most of the CPU boost functionality ad much as I can and runs very smooth so far with interactive.
[ONE Original Android Development] tmotard:
Hi. What is a good value for vfs pressure in your case ?

?
[ONE Original Android Development] LiquidSolstice:
Booted on first try! And is still just as beautifully smooth as the ones before it.

Whatever the gremlin was, I think you finally nailed it!

EDIT: Also, it could just be me, but I almost feel like screen wakeup is faster (with DT2W).
[ONE Original Android Development] renaltosonylevi:
Howdy!

I finally got one of those newfangled oneplusses.

First I have got to say having previously been a lg g2 user you guys have your expectations set way to high.:) Success for a g2 is "well it didn't brick this time". Seriously, things work so well it is almost boring!

Having flashed r13 on vanir_exodus 5.1.1 0605 all seems fine and smooth etc.(this is not a review) No bootloops!

But every time I try to change the GPU governor it's freeze and reboot.

https://docs.google.com/file/d/0B5Cnx7ECUwEkSHdfUkhQRmt0VVk/edit?usp=docslist_api
[ONE Original Android Development] Norapapa:
R13T3 works with euphoria 2.6. No bootloop. But many errors in Synapse
[ONE Original Android Development] renaltosonylevi:
I have the same issues.

You mean all that stuff is not supposed to be red?:eek:
[ONE Original Android Development] HaTrED_:
Guys, that's a new rebase from previous kernel so some settings aren't available - yet!
[ONE Original Android Development] renaltosonylevi:
True I appreciate that but render did ask for reports of reboots and other issues.:)
[ONE Original Android Development] schaggo:
[MENTION=5438598]RenderBroken[/MENTION] how should one interpret values like "20000 1400000:40000 1700000:20000" for governor tunables where according to internet research a single value like "30000" is expected?

Do these numbers signify multi-step-values? Like (above numbers) default 20k, from 1.4GHz onwards 40k up to 1.7GHz and then 20k again?
[ONE Original Android Development] RenderBroken:
Interactive is a unique governor in that we can set multiple update rates. This means that's the update rates slows down when freq is above 1.4ghz then speeds up when above 1.7ghz. So what this means is the governor slows down its thinking while at the optimal freq of about 1.5ghz then when its above 1.7ghz it speeds up its thinking so it can make faster decisions about whether or not to stay above 1.7ghz which in turn usually makes it scale down faster when the workload is taken care of instead of just hanging at higher freqs for no reason afterwards.
[ONE Original Android Development] RenderBroken:
I am getting lockups at:

update_task_ravg

So expect some reboots caused by this this piece is integral to the new scheduler/cpu boost. If I can get it to work then I have to scrap it while keeping all I can of the new changes.

On another Note, I believe dt2w is waking faster as well and I am curious if it's the io sched being row instead of zen. If someone can test and let me know that would be cool. This means that I am on to something though and even if I have to scrap the new changes, I will continue with the rebase.

You cannot change the gpu governor to simple_ondemand yet. There is a bug when its enabled that causes a reboot. I know the fix so hang tight on that.

Synapse will not have alot of tunables in the meantime as well.
[ONE Original Android Development] RenderBroken:
Awe snap! Made some new changes and Have not had a reboot yet! (Knock on wood!)

I am going to add in a few more changes then release a new build.
[ONE Original Android Development] mp3deviant721:
I've tried to set the I/O to row/deadline/tripndroid on R11 that never seemed to make the wake up faster. Haven't tried the test kernel yet though, I will tonight and report back.

OnePlus One | EuphoriaOS x Boeffla edition™
[ONE Original Android Development] _ASSASSIN_:
I said... 10% for BOTH VFS and swappiness
[ONE Original Android Development] Snuzzo:
[MENTION=5438598]RenderBroken[/MENTION]

Remember what I showed you about deadline? Give it that change and try that as your default instead, becomes faster than SIO and better on battery than Zen.
[ONE Original Android Development] abhi08638:
Oooh secrets? I wanna know too:D

I've been trying deadline too but in a way that makes it prioritize reads over writes more aggressively
[ONE Original Android Development] Flak:
Had a random reboot while in the car streaming Pandora over bluetooth.

DU Test 6/3/2015

Render R13-T3

Just had another reboot while posting this from a pc. Had just copied the first log using ES over wifi to my server. Closed ES and let the phone be. Right as it was about to sleep it rebooted.
[ONE Original Android Development] abhibnl:
And what are those changes? [emoji12] [emoji12] [emoji12] [emoji12]

Sent from OnePlus One
[ONE Original Android Development] RenderBroken:
I dont remember, We have discussed alot of development lol. [MENTION=3419683]Snuzzo[/MENTION] Would you be so kind to drop a knowledge bomb on this thread my friend?

ALSO I have been steady at work trying to resolve the random reboot tied to the new scheduler code. I have been rolling back many changes that I believe have a hand in it. Please test this new build and report and Reboots along with provide log info. The easiest way to provide log information is to use the app called Syslog. Just get me all logs to keep it simple. Thanks guys!!

R13-T6
[ONE Original Android Development] Jole7:
Hello guys i searched for tunables on deadline and i found some here https://groups.google.com/forum/#!topic/francosdevteam/ujjpcYsroHo[1-25]

if you want give it a try i've used them before and were working well now i use fiops.
[ONE Original Android Development] RenderBroken:
Thanks for sharing!
[ONE Original Android Development] RenderBroken:
Just in case you missed it, I have a new test build a couple posts above. Please test and report back. So far I have had 0 reboots.
[ONE Original Android Development] slebit:
I use it right now on validus. No issues so far. Thanks for you work!

I used your kernel when I had LG G2, I loved it back then also!
[ONE Original Android Development] RenderBroken:
Glad to have a fan! Never would have thought that my kernel would be as popular as it is. Just shows that my hard work pays off in unexpected ways. Thanks!
[ONE Original Android Development] schaggo:
Are you kidding? You provide us with an exceptionally well put together kernel.

I tried most kernels out there, especially the "big" ones but always found myself coming back here.

Even wanted to leave CM for Omni, but there I wont be able to enjoy your kernel... ?

I'm trying to upload some last_kmsg I captured running the previous to last kernel from a couple pages back - they're too large though. Humpf

Had a handfull of reboots today and captured the logs. Seems like a "controlled" crash reading the last couple lines of the logs. Hope they serve the purpose. I'll flash and check out the latest test upload tomorrow.
[ONE Original Android Development] LiquidSolstice:
Flashed just fine, no bootloops. I did have a few reboots with the last test during BT (but I was in the car and couldn't log it), but this time I'll be prepared for one.

I do notice (although I realize you probably expect it) a little more lag and choppiness in certain scrolling animations (such as pulling down the bar all the way to show QS) or scrolling through settings, but I imagine that's because you're still adding back features to your kernel.

Thanks for all you do!
[ONE Original Android Development] RenderBroken:
Thanks for the logs guys and the kind words! Now to confirm, these are reboots are NOT with r13-t6 correct? So far I have still have had 0 reboots. If you are still having reboots, make sure you downloaded the newest test build a couple posts back. Thanks gents, and maybe the random lady!

Also double check the hotplug settings. I still need to tie up scripting and found that stock qcom mpdecision and msm_hotplug were both enabled. This can Def degrade performance. I have also had no lag what's so ever.
[ONE Original Android Development] LiquidSolstice:
Correct, no reboots on T6. There were reboots on T3.

I'll check to see if both hotplug and mpdecision are enabled. I haven't used Synapse in a long, long time on this kernel. Does it require the official UKM to be flashed first?

Thanks!
[ONE Original Android Development] schaggo:
Yes, logs are from R13-T3. Just booted up R13-T6 for the first time.

It feels snappier than T3, but this could very well be placebo.

I did not have any lag on T3 either, but I might add that I customised Hotplugging and governor.

---------- Post added at 01:23 ---------- Previous post was at 01:15 ----------

No, customised version available in OP.
[ONE Original Android Development] SanXacobe:
Also happy to report no reboots with the latest T6, whereas the previous test kernel would reboot fairly regularly. Definitely a smoother ui experience when compared to other kernels but it does drop a few frames when compared to your buttery previous smartmax defaults. Keep up the awesome work and I'm looking forward to seeing what tweaks you have in store for us next!
[ONE Original Android Development] LiquidSolstice:
Derp. Didn't even think to check the OP. XDA medal of shame goes to me :P
[ONE Original Android Development] RenderBroken:
Holy crap guys. I still have had 0 reboots. . . I have been trying to fix this reboot issue since day 1 when I first started to build my kernel for the OPO. It took me about 70 builds. The first 40 were dealing with these reboots because I REALLYLYLYLYLYL wanted to make this part of my kernel base. But I was dealing with reboots and could not figure out why. Well I decided to really dig deep and find the issue. I have reverted many changes to get to the point I am at right now. I know other Kernel Devs were running into the same problems so I have marked my reverts dealing with the associated changes by adding "TESTING!!!" to the front of the commits. If this continues like it is, I will really ramp up the rebase.
[ONE Original Android Development] jduenes:
Is anyone else having problems with synapse? Or am I just missing some information I probably read past? I really cant adjust anything. Its showing seekbar has failed in a lot of options. Other than that all good. Booted fine on T6. Again sorry if I missed something stated earlier if it is already mentioned!
[ONE Original Android Development] LiquidSolstice:
There will of course be a lot of things missing. He stated he's rebasing and cleaning up to try and figure out the bootloops once and for all. The UKM might be causing Synapse to show tunables that don't exist., because I imagine that UKM is meant for stable/mature releases.

I wouldn't mess too much with Synapse until his current testing settles.