yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
As for placebo, sorry, I believe you are having issues, I just meant that its seems placebo that its my kernel in particular. Interesting about the same happing with the other kernels with the new touch screen drivers. hmm. May be something there. Also No problem man, that's what I enjoy. Development is a fun learning experience for me. Can you try flashing r9 and let me know if the problem persist? R9 doesn't have any of the new Touch commits. Thanks!
[ONE Original Android Development] Snuzzo:
[MENTION=5804516]ponytojas[/MENTION]

Does this occur on ROM where you utilize the baked in kernel?

[MENTION=5438598]RenderBroken[/MENTION]

Realize it could possibly be even a result of digitizer failing ....
[ONE Original Android Development] ponytojas:
It works!! R9 don't have any issue. You're the man Render
[ONE Original Android Development] RenderBroken:
Sounds like the new touch screen firmware stuff is not playing nice for you. Very interesting. Still r9 is solid and one of my best builds. Hang tight till cm can work on the touchscreen issues more.
[ONE Original Android Development] sneakerspark:
If there were a vote about who is the most helpful Dev in the community, i bet [MENTION=5438598]RenderBroken[/MENTION] would win it by miles. I'm amazed and equally happy to see that how descriptive, assuring and equally helpful his answers to every single query are.

You Sir have my #respect.

PS: i hope your new born and family is doing very well. Always love to interact with you. :thumbup:

Sent from my ONE
[ONE Original Android Development] neobuddy89:
I agree to that. Keep up [MENTION=5438598]RenderBroken[/MENTION].

And congratz RB for new born. :)
[ONE Original Android Development] RenderBroken:
Awe shucks. . .

Thanks Guys! Really means alot!
[ONE Original Android Development] Nandeh:
Agree with that too. Every comment done by Render is a lesson in development and humility.

Don't change and greetings for your new born, I just got a daughter too last Saturday and is best experience I have got in my life :)
[ONE Original Android Development] RenderBroken:
It is a beautiful thing. Congrats on yours as well!
[ONE Original Android Development] RenderBroken:
R14 is HERE!!

Download

Things to note:

This is a maintenance build with a few cool things added in. The main thing is Adreno_Idler

What it does it made it so the GPU actually remains at Idle for longer blocks when not needed. So far in testing I am blown away and there had be 0 issues with performance.

I am thoroughly impressed. Let me know what you guys thing but you need to leave the GPU governor alone. Do not change it to anything else to use this module.

Also to adjust the settings, all SYSFS files are here:

/sys/module/adreno_idler/parameters

So if you find that you don't like it, you can set Adreno_Idler_active to "N"

Changelog:

R14:

0910435 (HEAD, origin/cm-12.x, cm-12.x) Initial port of [MENTION=4898097]arter97[/MENTION] 's Adreno_Idler

8c181c7 PM: devfreq: Fix show available freqs

bb3460c PM: devfreq: Use high priority workqueue

b62af16 mm: slub: Default slub_max_order to 0

7cd7103 nohz: Reduce overhead under high-freq idling patterns

cef4400 crypto: add lz4 Cryptographic API

d5a1f0b Bluetooth: fix possible info leak in bt_sock_recvmsg()

55fdd6b Bluetooth: Fix invalid length check in l2cap_information_rsp()

806330e Bluetooth: Fix missing length checks for L2CAP signalling PDUs

2a4b437 Bluetooth: Fix crash in l2cap_build_cmd() with small MTU

b106c2e Bluetooth: Cancel power_on and power_off work

377086b Bluetooth: Prevent Bluetooth L2CAP Remote Heap Memory Corruption

fe811a2 ./Makefile: tell gcc optimizer to never introduce new data races

22bf312 Disable -fconserve-stack on ARM v2

b67e28c ARM: dts: A0001 Truly panel: Fix Mura

5cbca40 staging: alarm-dev: information leak in alarm_ioctl()

2c55c9c Revert "alarmtimer: set power off alarm to be triggered on time"

fc23f96 alarm : Fix the race conditions in alarm-dev.c

4df42db rtc: alarm: init power_on_alarm_lock mutex in alarmtimer_rtc_timer_init

6bd4701 qpnp-rtc: clear alarm register when rtc irq is disabled

c49d896 rtc: alarm: Add power-on alarm feature

eeeb07d staging: alarm-dev: Refactor alarm-dev ioctl code in prep for compat_ioctl

74142ff3 staging: alarm-dev: Drop pre Android 1.0 _OLD ioctls

ec1eb95 msm: kgsl: Bump the GPU frequency for long blocks of processing

2a70943 devfreq: gpu: added simple time_in_state stats

c336d8b msm: kgsl: check for NULL pointer access
[ONE Original Android Development] dahndahnbo:
Hi Render thanks for your know version but there are no link correct me if I am wrang
[ONE Original Android Development] 1337jay:
Yeah, he forgot to add the hyperlink - there you go http://renderserver.net/devs/RenderBroken/OPO/CM12/.
[ONE Original Android Development] RenderBroken:
Thanks! :D
[ONE Original Android Development] pijas82:
Well this kernel , its perfect, can use your synapse profile with this magnífic kernel.

Thanks

After i tested all kernels ,im back ever to render
[ONE Original Android Development] RenderBroken:
Glad to hear! It's always a good thing when someone has tried other kernels and has come back to yours.

Even I try other kernels from time to time. Keeps me sharp. Thanks for the kind words.
[ONE Original Android Development] ravvio:
Trying this kernel for the first time. I am on SlimLP 5.1.1 by fusion jack. Is this compatible or incompatible like Boeffla ?
[ONE Original Android Development] FullWipe:
Absolutely compatible :good:
[ONE Original Android Development] ravvio:
Do i need to flash ukm zip inorder to use Synapse or its inbuilt ?
[ONE Original Android Development] FullWipe:
Need to flash UKM in order to use Synapse

The first post, as in every 3d, shows all the details that you need then it's a good choice read the first post before asking :good:
[ONE Original Android Development] kalpik:
R14 is awesome! Any chance you could include screen color profiles?

Sent from my A0001
[ONE Original Android Development] ryaneu:
Hi Render.

I see that your kernel is still based on linux 3.4.107

Any particular reason why you're not moving to 3.4.108 yet?
[ONE Original Android Development] RenderBroken:
Not sure what you mean. Could you elaborate.

No reason, just had not updated to it yet. I started to but didnt want to mess up my working branch while I was working on Adreno_Idler. Afterwards, I just forgot.
[ONE Original Android Development] kalpik:
Well, if you see ak kernel, he has included popular screen color presets (amoled, etc) in UKM, so they're available in synapse. So instead of adjusting all screen parameters manually, I can just select a drop down from a list. Just a convenience feature, really!

Sent from my A0001
[ONE Original Android Development] RenderBroken:
Ok Yea, I gotcha. I am working on updating my version of UKM and that will be part of it. Thanks bro!
[ONE Original Android Development] ryaneu:
Render I have flashed your kernel for the first time.

I flashed UKM and installed Synapse too but I see many SSeekBar has failed: values in Synapse.

Any idea why?
[ONE Original Android Development] RenderBroken:
Yes, I had done a complete rebase of my kernel meaning I essentailly redid the entire thing. So some things are no longer present in the newer releases. I am

A) Updating UKM

B) Resolving the issues kernel side.

Really the problem stems from UKM looking for sysfs' in the wrong path. In the new Rebase, they are in a different location for some things. Regardless, the issue should not cause you to miss out on anything in the meantime. It would just be nice to get fixed up and it will be.
[ONE Original Android Development] ilfat12:
Hi!

At R13 and R14 phone goes to sleep and after a while does not wake up. If call this phone, also did not happen, but on the phone who is calling beeps presence.

I want to use this kernel, but unfortunately does not work.

Tested on the Euphoria and Resurrectoin Remix.
[ONE Original Android Development] 1ceb0x:
If someone is using this method to adjust the new feature, don't forget that once you restart, the modifications made under /sys/ will be overwritten.
[ONE Original Android Development] alpsayin:
Hi, I've been using RenderKernel since r9. I'm quite enjoying it, battery life improvement is superb. Keep up the good work!

That said, I'd like to report a problem with R14. When I updated to R14 my bluetooth headset's controls stopped working. In more detail; I can play/pause spotify but next/previous track button are no longer responding. But they were all working with R13. And they were also working with the CM kernel.

The headset is BSH10 with bluetooth v.2

Cm version is 12S with the latest update(YNG1TAS2I3).

I have made no changes to the synapse profile, I use it as flashed.

The device is OPO 64gb, TWRP Manager installed, and rooted with SuperSU.

I hope this information is of help, I can send more stuff if needed, just PM or mention me.
[ONE Original Android Development] RenderBroken:
Hmm, I have no such issue and you are the first to report it.

Can anyone else confirm this behavior? I use my phone for work and make calls all day and have not had this problem yet. Could you possibly get me all the logs you can using the app "Syslog" from the playstore? That would help tremendously.

I had made some small changes to BlueTooth. I too use a headset so I will test this out and see whats up. Thanks for the report! If there is an issue, I will just roll back the changes.
[ONE Original Android Development] ilfat12:
Logs:

https://drive.google.com/file/d/0B5tcudx9AusqcGJ0MTNmNF9mR00/edit?usp=docslist_api

Thanks:)
[ONE Original Android Development] TLengert:
I was having this issue on R13 as well and had to uninstall the kernel. Also, I found that apps ran extremely slow when the screen was off and made it almost unusable when playing music, podcasts, etc. Trying to pause music, switch songs, and even wake the screen next to impossible. The stock kernel from last nights nightly update is performing better than Render 13 and battery life is just as good, if not better. Seems this kernel might have crossed the line between performance and battery life? I switched back to R11 T6 and did not experience the screen wake issue or have any performance issues.
[ONE Original Android Development] ilfat12:
I reinstalled Еuphoria with 4 wipes and flashed Render kernel. Nearly three hours have passed and no problems. Before that I had Boeffla kernel. Maybe something left of him, but I took advantage of the special menu in Boeffla-Config for cleaning prior to installation of other kernel. I do not know whether this was the reason, but now Render kernel works fine.

Thank you and sorry to trouble ;)
[ONE Original Android Development] LiquidSolstice:
[MENTION=5438598]RenderBroken[/MENTION], is there a reason why the default governer has been changed to interactive? I was feeling like the UI wasn't as fluid as it once used to be, so I went and looked. The moment I set it back to smartmax, it was liquid smooth again.
[ONE Original Android Development] RenderBroken:
Really don't think this is an issue with my kernel. I have no such issues and others would be reporting the same. The only report close was the one about the screen not waking (I think that was the point) when there was a phone call. But then again, I have been testing that scenario all day with no problems. Have you made any changes from the Stock settings? Also could you let me know what Rom you are using? Definitely curious to get to the bottom of this. Something is not right that's for sure.

It was for testing. I was pretty happy with the outcome and was using slightly lower freqs. I think part of the problem is I need to bump up the input_boost_freq for cpuboost to account for the governor change. SmartMAX uses higher freqs on touch events than interactive.
[ONE Original Android Development] RenderBroken:
One thing I see is Thermal-Engine is logging so many errors its reaching the Audit limit. This is something I will change for R15 for sure. It is part of the stock Thermal Setup. I will also revert the Bluetooth changes I made and that should fix the problem. Thanks for the logs! IF all goes according to plan, I will release R15 tonight.

I mainly wanted to get Adreno_Idler out there for others to test and give feedback. One thing I noticed is I am getting more SoT and Playing videos is not as battery taxing as it was before.
[ONE Original Android Development] LiquidSolstice:
Ah, makes sense. If interactive can be as smooth as smartmax with the added benefits of better battery, I am all for it! I look forward to R15 and what you have in store for us next.

Thank you for your efforts, as always!
[ONE Original Android Development] schaggo:
Thats a somewhat weird conclusion, as in the end, Smartmax is in fact a (heavily) modified Interactive, to make it much more battery friendly.

Digging around and reading up on governors and tubables, I found the stock Smartmax values of this kernel somewhat irritating. I'd have to reset my setup to restore stock values to read them out though, as I am running a modifies setup ATM...
[ONE Original Android Development] LiquidSolstice:
Then I would assume that it has to do with the specific tunables Render is using (probably related to input boost, but I have no idea what I'm talking about when it comes to kernel tunables, so take with a grain of salt).

All I know is that smartmax is way, way smoother than any other governer and providse me with an iOS-like almost-60FPS UI.
[ONE Original Android Development] RenderBroken:
I mean this in all seriousness, please explain what you find irritating. I am not opposed to hearing someone out that may have a different opinion. Let me know what you would change it to.
[ONE Original Android Development] Flak:
Should we download R14 or wait for R15?
[ONE Original Android Development] RenderBroken:
R15 is HERE!!

Download

Things to note:

Cleaned up a few things and reverts some bluetooth commits. Also changes up default settings to go back to SmartMAX. Lastly, I disabled Stock QCOM Thermal Service. This will fix the issue where Audit rate limit is being reached in the logs. No sense it continuing with worthless errors. Also updated to 3.4.108 and brought inline with CM once again.

Changelog:

R15:

d8773c0 (HEAD, origin/r15-t1, origin/cm-12.x, r15-t1, cm-12.x) Revert "GPU: Set Initial Freq at 200MHz"

f5ab876 msm: vidc: removed the async v4l2 event for session unsupported

25a3a655 ASoC: Avoid wrong map/unmap of ocmem

d0b34bd Defconfig: Enable Adreno_Idler

b94e46b devfreq: adreno_idler: Clean up

2d22717 devfreq: adreno_idler: Use state notifier helper

03fef09 devfreq: Introduce Adreno idler for devfreq-based devices

bb53186 drivers: state_notifier: Export suspend status

ee82bb7 State_Notifier: Update Function for Backlight Control

1bb4d12 msm: Clean-up hotplug drivers

f0c89e4 drivers: state_notifier: Implement suspend_defer_timer

5b40b8c Linux 3.4.108

7b0f413 workqueue: block: remove WQ_POWER_EFFICIENT from kblockd

AnyKernel: Update Render Script

Disable Stock QCOM Thermal Service
[ONE Original Android Development] drdrewdown:
Thanks as always.. I hate to be that guy but I've always had issues with Bluetooth audio in my Hyundai Veloster until R14. While I've only got to use it a few times it hasn't stuttered at all (usually does for the first 5-10 minutes then works fine until I reboot the car/phone lol).

I'm curious if you could provide any info regarding the Bluetooth commits that you reverted in R15? I'm gonna test R14 again on the way to work tomorrow then give R15 a shot to see what happens.

In reality the few times I've had success in R14 might simply be luck/coincidence not sure yet until I have more time/chances to test. Looking at your changelog & github I'm not seeing the commits related to BT so any info you have would be great!

Many thanks in advance

Edit: it was a placebo, had skipping again this morning.. heh
[ONE Original Android Development] ak:
Thanks a lot my friend I have find the problem on my source.

Sent from my A0001
[ONE Original Android Development] Renosh:
Saw a couple people mentioning the color being different on this kernel (a little over saturated). I fixed it on R15 by going to

Settings>Display & lights>Screen color

Choose vivid then standard. The colors go back to normal.
[ONE Original Android Development] letroll59:
Anyone can help me to build this kernel with this patch? Or build it for me?
[ONE Original Android Development] RenderBroken:
I will take a look and see about adding it in. Can you tell me why you want this? Like why would it be helpful? I am always curious.
[ONE Original Android Development] RenderBroken:
F2FS support incoming. . .

I will not be responsible for any issues that occur when using F2FS. Make sure you understand the caveats and how to go from EXT4 to F2FS and back!

I am working on releasing R2 today!
[ONE Original Android Development] gianton:
Great news! T9 working very smooth and rock stable on Euphoria with stock settings.

Thanks for your work.

Edit: Would you consider adding the Smartmax governor?
[ONE Original Android Development] RenderBroken:
Thanks. Yea that is one I need to add. Thanks for the reminder.
[ONE Original Android Development] RenderBroken:
It has now been added.

I have alot more lined up for this release than I thought so it will most likely be tomorrow before I release.
[ONE Original Android Development] _ASSASSIN_:
Crying inside :c
[ONE Original Android Development] niko2931:
Great news for the SmartMax users! :highfive::highfive:
[ONE Original Android Development] smoki3:
Render have you tried uber toolchain?

I boost our phone !!!!!
[ONE Original Android Development] ahaq:
This is sweet sweet with Europhia! And yes if the new uber is there will be the sweetest!
[ONE Original Android Development] molonad:
Hi is there overclocking on gpu and cpu? For me very nedeed.. ? thanx
[ONE Original Android Development] gianton:
Only CPU ocing no GPU.
[ONE Original Android Development] molonad:
CPU from 144-2880? Gpu is not important
[ONE Original Android Development] gianton:
From 146-2880 MHz yes.
[ONE Original Android Development] RenderBroken:
Actually I added GPU OC to R2. Now max is at 640~MHz. CPU OC was already answered. But why is it needed? Just curious.
[ONE Original Android Development] störte:
Cant wait to try R2 :D
[ONE Original Android Development] schaggo:
Lol... http://xdaforums.com/oneplus-one/or...-kernel-r1-t2800871/post59548232#post59548232
[ONE Original Android Development] molonad:
i make few profiles , from fastest to best battery . in fastest i use cpu maximum frequency 2880 :) i like idea that my phone can be faster and in gta san andreas this higher frequency really makes difference :)
[ONE Original Android Development] DerRomtester:
Needed for what? It is useless.
[ONE Original Android Development] molonad:
its not , already answered
[ONE Original Android Development] clockworkstop:
Eagerly awaiting R2. Fantastic work, keep it up!
[ONE Original Android Development] Nandeh:
Hi Render! Nice to see you here. I used your kernel in Moto G, and I loved it. Just installed R1 over Euphoria and the experience is awesome, as expected.

Nice for your great work :)
[ONE Original Android Development] Flak:
R15 may be your best yet. Using it with robbie's cm and it's really really smooth.
[ONE Original Android Development] aakazh:
Hey bud

Does ukm work properly or is kernel adiutor is to be used?
[ONE Original Android Development] sneakerspark:
He wants to control his PC through his phone.
[ONE Original Android Development] threetwentyfizzle:
Hi guys, new to this forum, just got my OPO yesterday, I read the OP, but which version is compatible for stock CM12S? Thanks!
[ONE Original Android Development] RenderBroken:
Pretty much, my kernel works for all CM12 based builds. So try R15 if you want to use the newest version of my kernel.
[ONE Original Android Development] threetwentyfizzle:
Thanks for the response! Flashed and working great. One question if you don't mind enlightening me, as I get more familiarized with this device. I'm coming from the HTC M8 with the same 801 chip set, the custom kernel I ran used Qualcomm's MP Decision Hotplug with On demand (probably HTC's fine tuning), and it ran super fluid, and was able to achieve 4 hours SOT off the significantly smaller battery in that phone.

You mind explaining how this kernel setup governor and hotplug differs, and what optimum settings to achieve the smoothest ui experience? And what's an average SOT on this device? I know that's a loaded question with a lot of subjective answers, but just curious to see how the kernel scene is doing it up with the 801 chips on this device :)

Thanks again, definitely feels noticeably smoother and less stuttery than the stock kernel, and can't wait to check some aosp roms out soon!

PS does this kernel or chipset on this phone allow for higher quality audio i.e. flac, 32bit audio playback like on the M8? From my understanding, this was due to the DAC on the 801 chip, and the Sense GPE kernels had the HD Audio Kernel Commits added, and made worlds difference.
[ONE Original Android Development] Blodgarm:
Re: [Kernel] Render Kernel [CM12.x][R15][Synapse]

Well, with some tuning I can get about 5-6 hours of sot, and it'll still be smooth. This is with moderate usage though, and using amplify and greenify. Oh and with no, or light gaming.

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] threetwentyfizzle:
Mind sharing your setup? I use Amplify and Greenify as well, definitely makes a difference for improved deep sleep and reduced wakelocks for me
[ONE Original Android Development] Blodgarm:
My entire set up? Or just amplify, greenify?

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] threetwentyfizzle:
Kernel tuneables if you don't mind. Governor and CPU boost tweaks if any, I'm leaving the preset defaults alone for now, as I'm sure the Chef deemed optimal for default. I'm just wanting to squeeze just a tad more swift fluid scrolling, not that it's bad at all now by any means.
[ONE Original Android Development] letroll59:
I wants to control my PC through my phone, by example with that I can do an application which will write my password and/or my two step authorisation code for me. I can also use my phone to setup thing on my raspberry pi.
[ONE Original Android Development] RenderBroken:
I was able to add it in. It should be working. I will PM you a test build. If you can test it out and let me know, I would be thankful. Thanks!

Also there is some cool new changes in the next build incoming. I decided that GCC 5.1 was stable enough to finally make the jump to it. I had optimized mach-msm/cpufreq (This deals with hotplugging) and SELinux as well. There are also a few other minor changes. All I know is the test build is noticeably faster. (No I am not just saying that) I can do certain things that I now see with 0 lag. Like fast scrolling through the calendar widget. When its loading more elements. Stuff like that. Still need to test further before releasing.
[ONE Original Android Development] _ASSASSIN_:
Is synapse being abandoned? last build I used had a lot of things broken in synapse to customize with the latest of your UKM.

Are you planning on just having users use kernel auditor? That wouldn't be bad at all tbh.
[ONE Original Android Development] RenderBroken:
Not at all! It's just low on the totem pole. Remember, I build this kernel for myself foremost. So there are things I want to have and use on my phone. At the moment, ukm is not absolutely necessary. Kernel Adiutor has filled a gap that remained a long time. You have trickster mod but it doesn't have the feature set and updates were getting further and further apart. So synapse filled that gap in supplying an easyish way to give control over kernel features. Still, I have been working on bringing ukm in line with my kernel again. Also, if Kernel Adiutor would add support for just a few more things, I would use it full time. As it stands right now, only a few things are in synapse and not in Kernel Adiutor.