yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] _ASSASSIN_:
If you want to not have a bias, release 2 mystery builds with only you knowing which one has the FPS tweak in it while the other is stock. Recommend users to not tweak with the settings for a day and have a strawpoll on which one felt smoother. Reduces placebo effect. Also make sure there are more than 30 participants.

My stats class has some use hehe
[ONE Original Android Development] Ofthecats:
Running r18. Came from ak.

The thing is that both ak and your kernel are great in the first place lol. They've always seemed smooth to me.

It is still early though. I'll post here if I notice improvements in ui

You're doing a great job. Keep up the good work.

On another note, what do you think about NR I/o requests set to 1024? I'm also bouncing between zen and tripndroid schedulers
[ONE Original Android Development] RenderBroken:
Not a bad idea. Thanks for the suggestion!

I have played with it without and real knowledge of it and it seemed to degrade performance to me when I ran IO Benchmarks.
[ONE Original Android Development] abhibnl:
This is an excellent and proven method to test something here on XDA. i remember the time when Archi was developing his ArchiDroid optimizations for galaxy s3 and he posted 2 mystry builds without giving any hint what is being changed. The result, no placebo posts and the users were sure that one of the builds was noticeably faster & smoother than the other. You should really go for a blind test to test your hypothesis. The conversation between [MENTION=4800121]Sultanxda[/MENTION] and you was really informative and i definitely learned something new today. Thank you guys!
[ONE Original Android Development] _ASSASSIN_:
Issue with archidroid's test was that he didn't have a large enough sample size to prove his results were statistically significant. It would be awesome if we could get a big pool here to see if our this tweak has any validity to it.
[ONE Original Android Development] RenderBroken:
OK Here are two new test builds. one has FPS set to 30 and the other has it removed:

R19-T2

R19-T4

Test both if you can and let me know which is smoother. I found one good area to test is the "Recents" tab from the Dialer. Cant wait to see what comes from this!

Please note your Vote with this poll:

https://strawpoll.me/4997475

Thanks [MENTION=6259574]_ASSASSIN_[/MENTION]
[ONE Original Android Development] _ASSASSIN_:
might want to hang on to this ;)

https://strawpoll.me/4997475
[ONE Original Android Development] abhibnl:
Well i'm sure we can get atleast 30-40 people to test it. I myself will try it this weekend. Also, users here on bacon have so much choices in terms of kernels that they switch alot, this is what i felt. But not the senior users like us who knows hor hard it is to get a kernel's tuning right to our personal usage. Oneplus sure has handed this excellent dev device in the hands of many noobs who just try stuff thinking it's cool rather than reading and gathering things thoroughly. :)
[ONE Original Android Development] threetwentyfizzle:
Testing T2, just flashed and initial impression is ok, but scrolling seems a little jerky, and fling distance isn't far. For example in Tapatalk, Contacts App, and Google Now.

On Euphoria 7/5 build, and according to Kernel Auditor, Slim is the default CPU governor?

Am I using your recommended settings? I left everything alone, just looking in Kernel Auditor on what settings are being used.
[ONE Original Android Development] RenderBroken:
No, smartmax is the default Gov. It looks like you are applying your own settings at boot.
[ONE Original Android Development] Sultanxda:
62 FPS is faster than 30 FPS (your UI would be noticeably laggier with 30 FPS).

Dynamic FPS is enabled via dtsi and the option is then parsed by MDSS. I tested it for funsies using the exact same options you used and the panel framerate stayed the same the entire time (62 FPS). You can check the actual panel framerate using an app from the Play Store called "FPS Test".

Dynamic FPS isn't compatible with our hardware either even if you were to forcefully enable it. A few months ago, I saw the 62 FPS issue and I tried adjusting the porch values for the panel to try and force it to run at 60 FPS instead... but the framerate never changed from 62 FPS, even with absurd porch values. The current dynamic FPS method you have set right now ("dfps_immediate_porch_mode") alters the panel's framerate via modifying the porch values... which doesn't work on our panel :p The only change in framerate I could get the panel to undergo was done by playing with some DSI clocks (I got it to drop down to 31 FPS and 16 FPS), and I couldn't fine-tune the framerate either. It seems like our panel (the JDI command-mode panel at least, which is the most common) only supports a few specific framerates: 16 FPS, 31 FPS, and 62 FPS. It won't change to anything else, so "dynamic" FPS isn't possible.

If you want to see what the display looks like when it's actually running at 31 FPS, add this line right below the dynamic FPS stuff in your panel's dtsi:

qcom,mdss-dsi-panel-clockrate = ;
[ONE Original Android Development] threetwentyfizzle:
OK, I'll uninstall the app and reflash kernel. Thx for the swift reply

Update: seems MUCH smoother now
[ONE Original Android Development] RenderBroken:
Ok. Thanks for the great info!

My understanding was that is could vary and I was setting the min limit that it could. But as I said, this is not my area of knowledge. lol

Thanks again.
[ONE Original Android Development] 1337jay:
Do you mind sharing your default smartmax tunables/values?
[ONE Original Android Development] usmani:
By can't tweak it I mean is, I tried to set two cores minimum but it won't take affect. Maybe a ukm problem. I asked for conservative version because the one ak or Franco are using is very snappy, the one in your's feels like the old one. Is it updated?

---------- Post added at 11:25 AM ---------- Previous post was at 10:40 AM ----------

One more thing, can you also add an option to light up the capacitive keys only when they are pressed? Like they don't light when screen is touched but only when the keys are.
[ONE Original Android Development] Jole7:
You are right i 've disabled hotpluging before and all 4 cores are on.
[ONE Original Android Development] störte:
Tried it again. Working now. Thanks

Send by Hyperdrive on one+One
[ONE Original Android Development] RenderBroken:
hmm. For now lets leave it here. If it gets out of hand we can open it else where. Thanks for the offer!

Sweet! Glad your happy. Let me know what kind of results you get.

Still haven't looked but I am pretty certain its a ramdisk issue. Just have to pull theirs and Diff them.

I was able to set MPDecision to 2 cores only after enabling MPDecision first. Conservative I believe is the one AK uses but will need to doublecheck. I have not seen anything regarding Capacitive Buttons. Does someone on the OPO have that ability?

Wonderful!
[ONE Original Android Development] schaggo:
I flashed R2 around 30 minutes before I went out to raid a nearby farm of the opposite faction in Ingress (the Google location based game). On the way to the farm I did nothing at all and let the device settle. I launched Ingress on-site and was surprised on how badly the device performed*. As the kernel runs totally default, I did not change any values and do not have Synapse nor UKM installed, did you change anything which could cause that?

*performing bad means laggy, stuttery, low framerate etc. Noticeably worse than my OnePlus usually performs.
[ONE Original Android Development] RenderBroken:
Nothing major, GPU had adjusted Init freq from 320MHz to 200MHz. I will download it and see for myself to see any issues. What Rom you on? Were you on my Test build before and if so how did it run? Thanks for the report!

Can anyone else confirm such behavior?

EDIT: What side are you on?
[ONE Original Android Development] schaggo:
Resistance :p

I was on R2 T5 as well as R2 T9, but did not undertake any takedowns in dense farms on these, only gameplay in my local, puny farm with only a handfull of portals. So I cannot tell.

Next time I go to that dense farm, I can try to remember to flash one of the T builds before I leave. Rom is CM12, yesterdays nightly. Official builds, no fancy toolchain builds or mods.
[ONE Original Android Development] gianton:
Even on stock settings I haven't noticed any lag on Euphoria.
[ONE Original Android Development] RenderBroken:
Resistance it is then!

To me it sounds like a memory issue. It could also be the new CM nightly doesn't play well with my kernel yet and needs to be updated. Keep me posted if you will.

Same here, I dont have any issues.
[ONE Original Android Development] gianton:
Here is my Synapse profile using with R2.

https://drive.google.com/file/d/0B8mXr0tbx63LbDJBRzZaYUgyOWM/view?usp=sharing
[ONE Original Android Development] usmani:
Not yet but boeffla said it's on his to do list. And yes I turned on mpdecision first. :p
[ONE Original Android Development] gianton:
What exactly do you mean? This is not Boeffla's kernel thread.
[ONE Original Android Development] usmani:
If you don't know what I'm talking about, don't bother replying.
[ONE Original Android Development] gianton:
It would be easier if you used either quote or mention.
[ONE Original Android Development] RenderBroken:
Test Build!

Playing with Tunings

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

Testing new Hotplug tunings for a smoother more enjoyable experience. Along with some minor changes in Ramdisk.
[ONE Original Android Development] smoki3:
Are you interested in making a cm12.1 test build :)

Want to try it on my rom
[ONE Original Android Development] RenderBroken:
Sure, why not? lol I think really the only thing I need to do is create a new ramdisk. I will do that today and report back!
[ONE Original Android Development] smoki3:
Thanks for that :)
[ONE Original Android Development] störte:
Cant resist to test the testbuild.

Did you ever think about to try a omni kernel ?
[ONE Original Android Development] funCrash93:
I see F2FS support, what about NTFS.? (for storage via OTG)
[ONE Original Android Development] RenderBroken:
[MENTION=5912374]1337jay[/MENTION]

Look at this file

/sbin/render-post-boot.sh
[ONE Original Android Development] 1337jay:
Got it, thanks!
[ONE Original Android Development] mittimus:
Flashed an hour ago T2 version on latest Exodus: zero lag, zero problem. Like it! So smoooth
[ONE Original Android Development] abhi08638:
I used the fps test app and it seems that the code for 30 fps may not be working after all. I assume the frame rate is so high (>60 fps) because the numbers on the screen are constantly changing but when you bring up the power menu (which covers the numbers) the fps dips to 9 or 10 fps
[ONE Original Android Development] Blodgarm:
I recently switched to an aosp based rom and I was wondering if the kernel is supposed to work on aosp based roms? I'm asking Cuz I flashed it this morning, it worked fine. About an hour or two later my phone shut off and went into a bootloop. I fixed it by reflashing ak kernel, so I feel like the render kernel caused the bootloop.

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] RenderBroken:
What Rom? Also logs would be nice to give you a definitive answer. But, since no one else is having issues (So far) I don't think that its just my kernel. Could be changes you have made and such. Did you make any changes with the default settings?
[ONE Original Android Development] Blodgarm:
Broken os and nvm I think the issues gone. I relfashed it and it's working fine now. I have a question though, I put the max clock speed to 1036 mhz but the cpu's are still jumping to frequencies over that. How do I make that stop?

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] 1337jay:
Overclocking and underclocking is disabled for now I think.

EDIT: http://xdaforums.com/showthread.php?p=61972262.
[ONE Original Android Development] Blodgarm:
No I mean that I set the max for all cpu's to 1036 mhz, but they still jump to 1958 mhz.

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] thoiloidainhan:
We are 50-50 on the poll result now lol
[ONE Original Android Development] RenderBroken:
Not certain. I would have to look into it. I have seen the Thermal Driver override this before. Since I use Franco;s Thermal control. That could be on e of the steps if your phone is overheating and it has a tendency to override whatever you set the Max Freq to. I could be wrong though but I think that's what I remember correctly.
[ONE Original Android Development] Blodgarm:
My phone wasn't heating up, and I seem to have fixed it. I just set it to 1190,then back to 1036 and the frequencies stopped jumping over 1036. Thanks for the quick reply.

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] 1ceb0x:
on a pool that was released a few hours ago. how do you guys even have time to test both variants in a few hours and draw a conclusion? :)
[ONE Original Android Development] threetwentyfizzle:
I haven't had an opportunity to try both, but R19-T2 has been smooth enough and battery friendly that I haven't been tempted to try the other test version lol ??

And Render, have you had any luck checking out Fauxsound?
[ONE Original Android Development] RenderBroken:
That fine, if you are happy, stick with it. Also, I have looked into Faux Sound and am still working on it.
[ONE Original Android Development] Flak:
Just trying one of the test kernels kind of defeats the purpose of the poll.
[ONE Original Android Development] threetwentyfizzle:
Gonna try out the other test, T2 is pretty damn smooth, and gave a good baseline to measure off of the last couple days. Will report back shortly ??
[ONE Original Android Development] 1ceb0x:
I would say, use the pool to decide which is the best for you and don't post your findings because then people can be 'influenced' by what they read and the end results will be erroneous.
[ONE Original Android Development] RenderBroken:
R19 is HERE!!

Download

Things to note:

Updated inline with CM and new Touchscreen Firmware

MDSS panel power savings

Updated LMK Some more.

Hotplugging optimizations

Changelog:

81979f6 (HEAD, origin/cm-12.x, r19-t1, cm-12.x) synaptics: Update find7 touchscreen firmware

ada954c mm: vmpressure: scale pressure based on reclaim context

cb4a90a arm: msm: Remove MSM_CPU_FREQ_SET_MIN_MAX related config

43811ad sched: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW

dcb61a9 cpusets, hotplug: Restructure functions that are invoked during hotplug

72217b9 cpusets, hotplug: Implement cpuset tree traversal in a helper function

d9eca09 sched: Simplify can_migrate_task()

c3cad6e Disable Dynamic FPS in DTSI File

39c8389 arm/dts: msm8974-mdss: Specify low power current load for DSI regs

4eadd2a msm: mdss: dsi: add support to configure regulator low power mode

fa9557c msm: mdss: io_util: add new API to configure regulator opt mode

adb86f5 regulator: add notifier event for regulator enable

5cb2189 msm: mdss: disable CX rail when entering idle power collapse

84f383f msm: cpufreq: Break early if target freq is current freq

882fb8e Trace: Add missing file for LMK Commit

e45ac0b drivers:lmk: Fix double delete issue

de01c81 staging:android:lmk: read rb tree root with spinlock

bec0a6c lowmemorykiller: set TIF_MEMDIE before send kill sig

845131b staging: android: lowmemorykiller: skip dying or exiting task

674c205 lowmemorykiller: adapt to vmpressure

bdee795 Revert "trace: allow memkill tracing to be selectively enabled"

36f2037 Revert "trace: memkill: trace LMK and OOM kills"
[ONE Original Android Development] RenderBroken:
The next release will most likely be a CAF one. Stay tuned :)
[ONE Original Android Development] Ofthecats:
Does setting custom lmk and vmpressure interfere with these new commits?
[ONE Original Android Development] RenderBroken:
Well. . .i have been playing with the new LMK Features and I am seeing alot (I mean ALOT) of:

init: Untracked pid closed with status . . .

It is alittle conserning to me so i have disabled it by default for now. With that in mind I had made another commit that should scale VMPressure automatically:

See: https://github.com/RenderBroken/msm8974_OPO_render_kernel/commit/ada954c2ba52acb6f70a15895df2704676c97785

But I will keep messing with it to see what comes of it. If you want to test and report back, I would appreciate it.
[ONE Original Android Development] Jet70355:
Can't wait for this [emoji1]

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] mp3deviant721:
I hate to be that guy, but what features do you plan on adding in addition to your usual features? I'd honestly love to see a multiboot compatible kernel with S2W... Plus your features.

OnePlus One | Euphoria OS x Boeffla edition™
[ONE Original Android Development] _ASSASSIN_:
[MENTION=5438598]RenderBroken[/MENTION]

You might find this very interesting...

http://xdaforums.com/showpost.php?p=61616611&postcount=566
[ONE Original Android Development] RenderBroken:
Yes, I will have MultiRom support. I dont care for Encryption. If you really want it, I am sorry. Dont lose your phone while being a double agent. . .

S2W is something I want to add to both kernels. Really My main focus will be the bringup of the CAF kernel. Then I will work to get them to the same maturity so I can make the same commits to both without having to add a completely different kernel to code for. I want to make this as easy as possible.

Yea, I have already looked into Partial Resume and even played with it. But the main thing that I seen it used for was for Wifi. The code dealing with Partial Resume and Wifi is for Broadcom, not prima so it was largely unuseable. I may have coded something to make it work but I am not that good lol. Still i will take a look. As always, thanks for the info. You know I am ALWAYS interested in cool android code!
[ONE Original Android Development] _ASSASSIN_:
I was thinking more about the GPU governor
[ONE Original Android Development] 1ceb0x:
Nothing new there. We have slumber step in our GPU with this kernel. Correct me if I am wrong, [MENTION=5438598]RenderBroken[/MENTION].
[ONE Original Android Development] RenderBroken:
Yes, we do have that step but I see what [MENTION=6259574]_ASSASSIN_[/MENTION] was thinking about. I will test it out and see.
[ONE Original Android Development] RenderBroken:
The new CAF build is going very well! Really excited to see this come together. Also I would like to thank [MENTION=4800121]Sultanxda[/MENTION] without his work this would be possible!
[ONE Original Android Development] nadiros:
I have been using your kernels on an unofficial AOSPA-L and its my understanding that I probably won't be able to test the CAF versions.... Something to do with the non CM based ROMs? Anyone have information about this?
[ONE Original Android Development] Ofthecats:
I'm so excited! R19 running great. I'm using a modified ukm zip from ak kernel thread made by abhi. He added values to enable dynamic vmpressure

Will you update your ukm zip with the next kernel? No real issue using abhi modified though
[ONE Original Android Development] RenderBroken:
You are correct, for the time being they are using cm device trees and HALs.

I will check it out. I may do so. I know it's been overdo. I just have alot of other dev projects going on at the moment. Still I am sure I can squeeze out a new ukm build.
[ONE Original Android Development] renaltosonylevi:
Not surprising after the warning you gave but darkobas-omni+sultanxda caf got stuck on the boot logo. But works fine on the latest caf cm build.

Nice to finally see the option of under volting. I am using kernel auditor right now but would I be better off with ukm and synapse?

Edit.

At the moment any attempt to change voltage results in reboot with kernel auditor.
[ONE Original Android Development] spr33:
Have you see much in terms of performance or battery increase with the CAF ROM compared with standard CM12? I've been tempted to go CAF for a while now but haven't seen anything conclusive in terms of performance/battery increase.
[ONE Original Android Development] markvd90:
[MENTION=5438598]RenderBroken[/MENTION]

For some reason I am unable to boot with sultans build, it just reboots on the 1+ logo.
[ONE Original Android Development] renaltosonylevi:
I got sold on what was at the time (2 months ago)a big improvement in smoothness and possibly 20% more battery and it addressed some issues I was noticing with the touch screens high noise threshold which was making my keyboard miserable to use. Won't show up in benchmarks though.

To me I regard these caf3.4 kernels as one of the more significant developments for the oneplus one. The only issue is that Sultanxda has quite firm views about what he will put in to his kernel or to be precise what he won't put in. So I am glad to see other developers get involved.

+Renders kernel threads are always a joy.

Though don't ask me as I am clearly biased.:p
[ONE Original Android Development] markvd90:
Did you flash the kernel on a clean install?

I did that, but it won't boot.

Not sure what is causing the issue..
[ONE Original Android Development] mp3deviant721:
I'm having the same no boot issue on Euphoria as well, just gets stuck on the OnePlus logo and reboot. In my case I'm trying it as a secondary. I'll try it as a primary later tonight as well as on CM12.1 CAF.

OnePlus One | Euphoria OS x Boeffla edition™
[ONE Original Android Development] RenderBroken:
lol thats how it goes. AnyKernel was causing it to not boot so I had to go the Ol' Ramdisk included route. . . I will look at other roms to see if I can make them compatible. Thanks for the report!

One word: Yes.

I have seen an increase in all areas. Multitasking is faster as well with apps opening much faster.

Not sure. Let me know if you get it to boot.

What is your flashing process?
[ONE Original Android Development] markvd90:
Wipe cache, data, system and dalvik.

Flash ROM, gapps and kernel.

In that order.
[ONE Original Android Development] RenderBroken:
And this is the reason I like to use AnyKernel lol. Thanks just wanted to check. I am looking into it now.
[ONE Original Android Development] RenderBroken:
Fixed Voltage bug. I will release a new build soon. I want to look at ramdisk first.
[ONE Original Android Development] sneakerspark:
Let me add one more thing, device heats up less. With non CAF buils and cm12.1 when i play clash of clans, cpu bumps up to 60 degrees in no time. Well now with CAF build which is underclocked to 2ghz cpu temp rarely crosses 50 degrees.
[ONE Original Android Development] RenderBroken:
I removed the under clock. If you still want to use the underclocked freq, just set it so using a kernel settings app. But yea, it would def help with temps. I also removed the stock Thermal driver and re-added Franco's. Its also ALWAYS ON. I made the mistake with Sultan's stock build and restoring apps while charging lol. SOB was HOT!
[ONE Original Android Development] renaltosonylevi:
Me ? Restored backup of caf cm12.1 .

Dirty flashed latest cm build (25/7) let it reboot and initialised apps. Reboot to twrp 2.8.6.0 and flash kernel and reboot again.

Success:)
[ONE Original Android Development] kalpik:
Just wanted to report that phone reboots as soon as synapse applies settings at boot (I didn't touch under volt). Uninstalled synapse, and it's fine for now.

Sent from my A0001
[ONE Original Android Development] RenderBroken:
Thanks.
[ONE Original Android Development] roemicha:
No issues running CAF-R1 kernel on Unofficial Euphoria 7/25. Cleared dalik and cache before flashing. Also no issues with synapse. Very smooth and fast. Excited for R2.
[ONE Original Android Development] _ASSASSIN_:
it would be super interesting to see 3.4.108 on the CAF version since I don't think anyone else's CAF version has it ;)
[ONE Original Android Development] usmani:
On caf build Cpu is spending a lot of time on 960000. Is it okay?
[ONE Original Android Development] RenderBroken:
That would be a crap load of merge work to do lol. I have already looked into it. We will have to see.
[ONE Original Android Development] DerRomtester:
This is not the idea of CAF.