yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Pepsy89:
smoki3 - ohh ok , i will try greenify hope this will work.
[ONE Original Android Development] RenderBroken:
I have one last thing to change and see if it helps before I revert back to what I had with R6. I will release a new build within an hour or so.
[ONE Original Android Development] _ASSASSIN_:
Are you considering using Uber 6.0 now or is it not stable enough?

Also a question about the graphite optimization, does that actually give enough of a benefit to consider or does it cause too many errors in the build process.
[ONE Original Android Development] RenderBroken:
I am still going to wait a little bit longer before I really start to use 5.0 or even 6.0. I know that 4.9.3 is proven. I cant say the same for the others. Now will I never release a test build using the two? Naw, I most definitely will. As for Graphite, right now when I use it I get a no boot situation. I know the exact flag that causes it but really I don't think its worth it, I have not seen any real gains with using it. Alot of times I ask myself, why don't major Rom teams or Google use xyz feature/change/etc. If it was such a good idea then ppl much smarter than I would be using it. Still its always fun to test and see.

New Test Build!

R8-T3

So I believe that the issue is with using the new notifier driver ontop of use LCD notify as well at the same time. I think there is a race condition. I can see from some logs that [MENTION=4129455]Formhault[/MENTION] provided, that it looks like the backlight is on/off over and over (5x) till the log ends and thus an SoD occurs. So prior to this new build I left LCD Notify in for some minor features still waiting to be converted to use State notifier. So lets test my hypothesis. If I am right then good lets move forward! If I am wrong then I will revert back to solid ground lol.
[ONE Original Android Development] Formhault:
*clears throat* F2FS, FFS...
[ONE Original Android Development] _ASSASSIN_:
even though google did use one F2FS partition on the Nexus 9
[ONE Original Android Development] Formhault:
Hm?

One? So... F2FS is starting to take over. Well... all in due time, I guess.
[ONE Original Android Development] RenderBroken:
I believe motorola uses F2FS on all major partitions.
[ONE Original Android Development] _ASSASSIN_:
Yep, just had a SOD with r8t3 :(

Here is the last kmsg
[ONE Original Android Development] dolbylogic:
One SoD using R8-T2... Will try R8-T3...
[ONE Original Android Development] RenderBroken:
I actually do have one more thing to try before completely ditching everything. I will also run a build with it just to be sure. then after that, I will revert if it remains. Thanks for your help. Just a major waste of time for something that shouldn't even be an issue. . .

EDIT:My head just explodededededed. . . . . . .

Ok I see where I borked. I setup the new Backlight method for the new State notifier Driver but I didnt actually use it. . .I know. . .you dont have to say it. . . .

So, I am about to release R8 that has been properly fixed. The previous method was still using the MDSS method which was causing the SoDs.
[ONE Original Android Development] LiquidSolstice:
I was about to inform you I've been on R8-T1 since the day it was released, and I have not had a single SoD. Running on Euphoria.

You are doing amazing work, I'm annoyed I never tried your kernel before. It's smooth, and quite efficient. Thanks!
[ONE Original Android Development] RenderBroken:
Thanks! Glad you like it!

Yea this just shows why all phones are actually underclocked to some extent from the factory. Because they are not all the same. The SoC Makers KNOW that they should all be able to handle say 15% less than what they are rated so they ship them all that way regardless if the device can handle otherwise.
[ONE Original Android Development] LiquidSolstice:
Makes sense. For what it's worth, because your kernel is so smooth out of the box, I didn't even bother flashing UKM/Synapse. I'm using whatever stock settings you built the kernel with, because after all the SoDs I was having with ak's kernel, I badly wanted stability, and I got it. No underclocking, undervolting, or other tweaking required. It's nice to have a flash-and-forget solution.

Consider this a much more substantial show of appreciation: 9HE070262A026274V

Keep doing what you're doing.
[ONE Original Android Development] RenderBroken:
Really, thanks!

R8 is here!

Download

Changelog:

R8:

46694f8 (HEAD, r8) CHROMIUM: cpufreq: interactive: validate above_hispeed_delay

e457822 cpufreq: interactive: Honor boosted state in several timer calculations

2fc0fee cpufreq: interactive: Consider changed min limit a frequency boost

f381b17 cpufreq: interactive: Honor changed minimum frequency

57c99a6 cpufreq: interactive: Record hispeed_validated_time in timer function

7cfd80e cpufreq: interactive: Exercise hispeed settings at a policy level

e72f5c8 mmc: sdhci-msm: Add Samsung 64G search after tune quirk

e870c22 (origin/r8) Revert "drivers: notifier: enable it by default"

2f9b15d drivers: notifier: switch to backlight solution

49c469a mdss: update from oppo

5091389 net: llc: use correct size for sysctl timeout entries

Should be good to go finally . . . lol no I can move on!
[ONE Original Android Development] NuLLV01D:
Flashing ASAP! I bet it'll be as smooth as the Audi R8... Lol
[ONE Original Android Development] _ASSASSIN_:
Render pls remove autoSMP I don't think anyone uses that. Could possibly say that for intelliplug as well.
[ONE Original Android Development] RenderBroken:
ASMP for sure, its on my list of things to do. Intelliplug will stay though. They really don't hurt anything other than make ppl scroll further lol. But I believe I will stick with msm_hotplug, intelliplug and bricked for sure.
[ONE Original Android Development] usmani:
How about mako hotplug, just as an experiment, in a test build? :)
[ONE Original Android Development] demon507:
Flashed R8 on Temasek and had soft reboots after building cache...it just reboots to bootanimation.
[ONE Original Android Development] usmani:
With a clean flash? Just flashed r8 over euphoria and it's working great.
[ONE Original Android Development] alexbk66:
What's the difference between Render-UKM-3.8.1.3.zip and AK.UKM_v3.8.1.9_Special_Ed.zip? Are they interchangeable? :confused:
[ONE Original Android Development] Zephyr!:
This happens when I try to restore the profile in synapse.
[ONE Original Android Development] aamitabh28:
Each is customised for its own kernel mentioned in the name.

Certain features specific to a kernel.. Most things are the same though

Its such a small download.. Download the the for the kernel you are running
[ONE Original Android Development] EasyGoingXD:
[MENTION=5438598]RenderBroken[/MENTION] may this kernel work for cm11 based roms too?

By flashing first the cm12 firmware and after that the cm11 modem? Is it somehow possible?
[ONE Original Android Development] Stinocon:
Thank you for this Kernel, i'm switched from Franco Kernel to Render because faster update.

Only two questions (i've already used Google and the search button):

1) I don't like Synapse app, is too muddleheaded, i prefer to use some application like Kernel Adiutor...

I need to flash UKM also in this case to obtain a full system/kernel manager integration?

2) Someone could kindly provide stock screen/color values? The defaults seem too prone to dark.

Thank you all!
[ONE Original Android Development] NuLLV01D:
Though you can use Kernel Auditor, some functionalities like per core control, etc can only be tweaked using synapse. And if you use this app, then no need to flash UKM.
[ONE Original Android Development] demon507:
Clean flashed yes. What i did was after flashing hold down the power button to reboot instead of reboot from recovery and it booted fine. Weird.

---------- Post added at 04:11 PM ---------- Previous post was at 04:08 PM ----------

@RenderBroken I've noticed micro stuttering during scrolling in apps using R7 and R8 while R6 was fine. It happens occasionally. Other than that kernel is smooth. Thanks.

Please take a look into it. I'm using stock settings R8 on Temasek.
[ONE Original Android Development] optimusG:
Where I can find the Render kernel specified UKM?
[ONE Original Android Development] aamitabh28:
In the OP?
[ONE Original Android Development] optimusG:
In the OP I can see the generic UKM file. I found it here. Thanks for the answer.
[ONE Original Android Development] RenderBroken:
The lag while scrolling is some rom side bug I have been reading about lately. I have no such issues though and always use the latest release. Still Thanks for the heads up.
[ONE Original Android Development] 1ceb0x:
I agree for ASMP, but please keep Intelliplug - I still use that **** from time to time, son!
[ONE Original Android Development] RenderBroken:
Here: Download

If you give the UCI error:

run this in terminal:

su

uci

uci reset

uci
[ONE Original Android Development] Alfiemarquis:
Been using render for quite a while and flashed r8 today with the latest nightly, stable and no sod, n anyone else noticed how colours are more vibrant with render?
[ONE Original Android Development] RenderBroken:
Do you like the colors? I believe its related to Sunlight Readability. I do set some KCAL settings on boot though. Something to make it not appear so cool.
[ONE Original Android Development] Alfiemarquis:
Yes I do, I have a crazily coloured wallpaper and it looks so much better with your kernel.

I have adaptive brightness on, but live display off, Al try the amoled settings on the first page.
[ONE Original Android Development] alexbk66:
Thank you for the reply. Just was wandering as UKM stands for

Universal

Kernel Manager?

Also (but not exactly sure though) I suspect that I had bootloop problems when I was actually using Render UKM, with AK UKM never had any issues.

Not because I'm lazy to download...
[ONE Original Android Development] Formhault:
My phone's been perfect for ~3 weeks. Then it went haywire. So I dunno. Maybe the digitizer was glued to the other side (not the chassis), and in time, it unglues... so it now touches the chassis... Man, I don't know. The only thing I know is that OnePlus f***ed up where no one really should.
[ONE Original Android Development] HaTrED_:
Been using Render's UKM since R6 till R8-T2 (where i'm at and will update to final R8 once i get an update from ROM) without a single issue! ;)
[ONE Original Android Development] nazfalas:
Yeah touch input seems kinda important on a touch device...

I guess this will be bye bye for my great OPO. I have disassembled one before for display replacement, but the risk of damaging my screen is just too big to justify that.

I have been able to reproduce cooling fixing it and heat causing the issue...

Hard to type this text now btw.

Sale it is then, but enough off topic now.
[ONE Original Android Development] Stinocon:
Ok, thank you! :)

---------- Post added at 05:15 PM ---------- Previous post was at 05:10 PM ----------

Yes, i've noticed it with Clash of Clans...

I have set "Screen Color" to "Standard" and it seems ok now.
[ONE Original Android Development] NuLLV01D:
First full charge cycle with R8 and 28/04 Euphoria. Heavy Spotify and Music, Tapatalk and YouTube. Seems Awesome to Me!
[ONE Original Android Development] 1337jay:
What's that theme/icons? Any tweaks btw, like Greenify or Privacy Guard for Play Services/Facebook etc?
[ONE Original Android Development] NuLLV01D:
Theme is BlakKat with IrideUI Icons. No tweaks used. Just blocked Wake, Keep Awake and Autostart for GPS
[ONE Original Android Development] 1ceb0x:
But, according to your screenshots, you only got like... 6-7 hours of up time and 5 hours of SOT....
[ONE Original Android Development] NuLLV01D:
the uptime is a lot less because i mainly listened to music and podcast. Trust me , no gimmicks here
[ONE Original Android Development] _ASSASSIN_:
With R8, I have had instances where I thought it was a SoD, but I just hit the power button for a couple of seconds and then it woke up. So I think the issue may be gone, but I'm really thinking the issue is with the feature that is the "prevent accidental wakeup", as once I disabled it, my wakeup times were much faster.

This is on the latest version of slimsaber.
[ONE Original Android Development] RenderBroken:
Very possible, I know my proximity sensor is hella sensitive. Drives my nuts cuz I talk on the phone through my bluetooth and need to brighten the screen sometimes and the damn screen will keep going off thinking I placed the phone to my ear lol.
[ONE Original Android Development] 1337jay:
Switched to your kernel cos franciscos is not updated for CM 12.1 yet, I'm pretty satisfied with all the configurations available and performance so far...battery life seems to be awesome aswell.
[ONE Original Android Development] 1ceb0x:
Battery life on R8 :)

Kudos bro, [MENTION=5438598]RenderBroken[/MENTION]
[ONE Original Android Development] vikrant82:
Please let the ASMP be.
[ONE Original Android Development] RenderBroken:
Awe. . Then I will consider it. It's not hurting anything. Thanks for speaking up.
[ONE Original Android Development] _ASSASSIN_:
Probably the best way to resolve it is to have a poll to see if a significant number of users actually use Autosmp whatever choice of hotplugging.
[ONE Original Android Development] vikrant82:
Thanks. I feel it's a simple yet powerful hotplug. Performant yet not too much switching on off cores.
[ONE Original Android Development] RenderBroken:
Can you tell me why you want it gone?
[ONE Original Android Development] _ASSASSIN_:
mainly just scrolling/overwhelms a lot of users. When each of these hotplugging methods all have very in-depth customizations, it can be overwhelming when you have 4 of them to deal with.

If you keep it at a minimum, it would be both easier to maintain for you and a better UX in terms of not providing them so many features that it just gets redundant and overwhelms a user with so many toggles and sliders which they may have no clue as to what to do.

The reason I strongly dislike Intelliplug is because he makes up so much of his own jargin you have to read up on it just to understand how to customize it. For me AutoSMP just seems redundant when we already have 2 hotpluggin solutions that attempt to imitate the stock MPDecision.
[ONE Original Android Development] RenderBroken:
Good points. Yea I agree that there is some weird naming in intelliplug. For me though, how each hotplug cores is different. I just have to think on it. At the moment everything seems to be running very well. I plan on cleaning things up over the next few releases.
[ONE Original Android Development] Almayce:
So I went ahead and tried your kernel and I must say it's pretty good. The smoothness is there and battery seems to be comparable to others(for me it's pretty much the same across kernels). What bugs me a bit are SODs here and there. Like every 20th screen wakeup is SOD. any ideas how to solve them?

Also I'm for autosmp & cleaning of the hotplugs. I come from mako and I ve grown accustomed to the Mirages kernel. He had everything tuned to

perfection. Simple, yet powerful. I believe in order for autosmp to really shine he tuned ondemand as well. But I could be wrong.

Anyhow, keep it up!
[ONE Original Android Development] RenderBroken:
So you have SoDs with R8?
[ONE Original Android Development] LiquidSolstice:
In my opinion, with the sheer complexity of Synapse and tweaking kernel parameters to begin with, "UX" isn't really relevant. Having the option to mess with a setting that ruins your ability to boot is how we learn to tweak. I think it's in the user's best interest to give them as much choice as possible, and let them figure it out.

I used to spend hours and hours agonizing over settings in Synapse. It was a ton of fun and I learned a lot, but these days, I don't even flash UKM, forget installing Synapse. However, even then, I'd vote to leave these things in, because unless they cause conflicts, or are known to cause serious problems, I don't see the benefit in taking them out.

There's a lot of stuff overwhelming about Synapse. If you can get over the initial hump of seeing so many settings, I'm sure you could get over a list that's somewhat longer because it has optional features in it.

I respect your opinion, especially concerning Intelliplug, but your opinion shouldn't dictate what options are available to users.
[ONE Original Android Development] LiquidSolstice:
As a side note, my friend flashed Render to his OPO and he ran into bootloops. I searched the thread and found a post where a user suggested waiting a minute after flashing, turning the phone off first, and then turning it on, and lo and behold, that actually worked. I also found a post that suggested that you might want to put this workaround in the OP. I don't know if it's just some weirdness with TWRP, but perhaps it might be worth putting this workaround in one of your main posts?

Just a suggestion.
[ONE Original Android Development] _ASSASSIN_:
I've been tweaking my android phones for the past 2 years. I personally LOVE customizing it with synapse since no other app can truly let me customize so many things at once. On kitkat on my HTC One M7, I had to install multiple CPU/system tweaking apps to get all the functionality I get from Synapse, so really I love tweaking.

Learning what a governor is and what I/O schedulers helps as these are applicable to all android kernels as well as linux itself. My issue is when all these developers make up their own terms for things leading to "unnecessary learning" similar to how windows does things, where you learn something that is ONLY applicable to their solution, it's just fluff to make your kernel settings sound cool.

I think a lot of the users are in the same boat as me where they know most of the tweaks they are doing but some of the terms in ASMP and intelliplug are very out there with no real context and not much documentation on them as well to make customizing it kind of a pain.

Also too much of the same doesn't really do much for anyone IMHO.

TL;DR- learning is good, but learning useless terms doesn't benefit anyone.
[ONE Original Android Development] Hash code:
Hey man..... Is there any guide where all the synapse settings r explained in detail..... Wanna learn them so that I can tweak stuff according to my requirement....

Ty......
[ONE Original Android Development] _ASSASSIN_:
Here are the basics + some of the development done here http://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
[ONE Original Android Development] vikrant82:
Poor ASMP guy exposes just 4 or 5 very intuitive options. And he's being blamed for being confusing to users?
[ONE Original Android Development] smoki3:
Maybe he means the long wake up time for some wakeups. But here with r8 no sod
[ONE Original Android Development] Almayce:
Yes. Just checked that I'm using R8.
[ONE Original Android Development] mrgnex:
No sods with R8 test 2. Great job!

Sent from my Bacon
[ONE Original Android Development] RenderBroken:
How are you trying to turn on your phone? DT2W? Power button? If DT2W, make sure you are not anywhere near the proximity sensor. Mine is like crazy sensitive and if I am near it I can kiss goodbye, opening my phone with DT2W. lol let me know. Thanks.
[ONE Original Android Development] Almayce:
Actually it's both, power button and dt2w too, but I think it has something to do with the proximity check in settings. I think I'm gonna disable it and check the results tomorrow :)

I'll let you know.
[ONE Original Android Development] RenderBroken:
Sounds good :)
[ONE Original Android Development] _ASSASSIN_:
the official R8 is the latest release buddy, you should get it.
[ONE Original Android Development] schaggo:
I was running smoki3's UberCM 12.1 build which comes with Render-sauce by default. Other than that, the builds are stock CM (apart from CameraNext, which is unrelated to SOD'ding). I was running the build from 28.4. since a couple days, which included one of the R8 test builds, quite possibly T2. Either way, the setup was running well since a couple days, I was happy.

Yesterday, without changing anything at all, still running the 28.4. build, out of the blue the device SOD'ded on me a couple times in a row. I managed to get two last_kmsg although I think one of the two is actually from after and not before the crash. Not sure though, not a pro in reading logs ;)

How it went: take device from pockets/desk, push powerbutton (proximity sensor is clear), capacitive buttons light up yet screen stays dark. I repeat pushing the power button a couple times, screen stays dark, buttons stay lit. After a while, buttons turn dark, screen still stays dark. From now on, buttons and screen stay dark. As the device did not come fully on after trying for about a minute (fast repeat push of power, repeat push of power with pauses, ...) I force-rebooted it holding the powerbutton. Interestingly, Android recreated the dalvik cache ("Optimising apps...") after the forced reboot.

All gestures are disabled as are DT2W and DT2S. Also proximity check is disabled. Kernel is running in stock configuration, neither UKM nor Synapse is installed. I was running a bit UV'ed but I don't think I was when it SOD'ed as I manually apply the UV after boot and I think I forgot. And even if I were, the slight UV was faultless for several days before even when heavily stressing the device without any issues. As said, out of the blue and in a row, without changing a config which was running well for several days and under heavy use, I'm a mobile junkie :p

2x last_kmsg:

https://dl.dropboxusercontent.com/u/23408386/last_kmsg-1.txt

https://dl.dropboxusercontent.com/u/23408386/last_kmsg.txt
[ONE Original Android Development] Almayce:
It seems (so far) the proximity wake was the issue. No sods as of yet :)
[ONE Original Android Development] _ASSASSIN_:
Hey [MENTION=5438598]RenderBroken[/MENTION] , I was looking at a random thread on the Nexus 5 forums, and I found a thread which had some decent information about intelliplug (mostly on how to configure it) as well as some of the configurations used in synapse for tweaking the governors (all in the OP).

Hope you guys enjoy it. Also thanks to [MENTION=6008473]Electrex[/MENTION] for all the great info!

http://xdaforums.com/google-nexus-5/development/electroactive-kernel-t3077596
[ONE Original Android Development] smoki3:
Yeah. Thats why we now use R8
[ONE Original Android Development] chiujiewei:
im on the latest cm12s stock rom..after flashing this kernel..why m i getting bootloop in the one plus one logo? keeps rebooting.. any help guys
[ONE Original Android Development] RenderBroken:
Did you clean flash cm12s? Also if so, it may be related to the transparent compression crap they pushed on us awhile back. R6 works for sure.l because it doesn't have it. Also that is the build that this kernel really started to shine.
[ONE Original Android Development] _ASSASSIN_:
My Color Setup

Here's my color setup, it's a warmer look kind of to replicate what the OnePlus used to have on kitkat with a little more contrast and saturation.

Here ya go!

Colors: 255,250,242

Min: 35

Contrast: 259

Hue: 0

Saturation: 267

Value: 252
[ONE Original Android Development] RenderBroken:
I will post in in OP when I get a chance. Thanks for sharing!
[ONE Original Android Development] aamitabh28:
Ill share my color profile as well!

Cooler profile for people who like cooler colors!!

Colors :236 238 256

Min:35

Contrast:262

Hue:0

Saturation:262

Value:251

Sent from my A0001
[ONE Original Android Development] RenderBroken:
Both have been linked. Thanks for sharing!
[ONE Original Android Development] Hash code:
Is there any other app except synapse which can help me set these values.... Ty....
[ONE Original Android Development] RenderBroken:
I believe kernel aduitor can. Also [MENTION=4316709]savoca[/MENTION] has a great app that can do it as well though I can't link it. Maybe someone here can post it.
[ONE Original Android Development] _ASSASSIN_:
[MENTION=4316709]savoca[/MENTION]'s color tweaking app

http://downloads.codefi.re/savoca/kcal
[ONE Original Android Development] NuLLV01D:
http://downloads.codefi.re/savoca/kcal

--EDIT--

LOL [MENTION=6259574]_ASSASSIN_[/MENTION] Beat Me!