yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
HOW DARE HE BE MORE HELPFUL?!! ;)

Thanks guys!
[ONE Original Android Development] kayrowl91:
Is it only me or after i flash the latest kernelmorese,,sde
[ONE Original Android Development] Nandeh:
Explain this mate, it's impossible understand as you wrote it :S
[ONE Original Android Development] kayrowl91:
Lol. What i want to explain is after flash this kernel,my touchscreen became unpredictable. Typing by itself. Thats why you dont understand what i said before.

Edit: after few reboots its look like my touchscreen is ok now.
[ONE Original Android Development] Norapapa:
I have a problem with R8 + ukm and euphoria from 03.05.

The charging animation works when I plugged the phone, but the phone didn't charging.

The original kernel works fine.

What's the problem?
[ONE Original Android Development] HaTrED_:
I've seen this post in other thread and seems quite interesting to all those mates that have/had SOD's:

http://xdaforums.com/showpost.php?p=60522073&postcount=1116

I don't/never use profiles so...:p
[ONE Original Android Development] RenderBroken:
Hard to believe, Especially since more ppl would complain of the same issue. Sorry bud, I don't believe it to be my kernel. I have a friend with the same issue and it was the same across everything. AK, Boeffla, My kernel. Stock rom kernels etc.

No idea as I don't even touch/change the charging binary or anything in the ramdisk for that matter. I just add to it with my script that sets kernel parameters on boot. So Its also hard for me to believe its my kernel but you never know. Unlike the issue above, I have not done any testing about this issue so I cant say. I will give it a shot and we will see. Thanks for the heads up!
[ONE Original Android Development] Norapapa:
I tested it twice. Every time a clean install. Charging is working properly. After your kernel installed. and charge no longer works.
[ONE Original Android Development] RenderBroken:
Ok I will give it a shot and test myself. Can you give me all the logs you can via syslog?
[ONE Original Android Development] IndDoc:
Go to synapse, look for charging voltage under misc. stuff - it is set to 100mA by default. Change it to 1200 ma, save, and enjoy. Done.
[ONE Original Android Development] RenderBroken:
That's not right. It's set to default charge levels. Is that what it was set to for you? Doesn't sound right at all. I don't set any levels at all and changed nothing of the sort in r8. When you flash ukm it sets what looks like the default level by checking what it's set to by the kernel and it appears as the default level in ukm. This is how many things are set up initially. Let me know. Thanks!

Also if it set that for you it should set it for everyone and its not that way for me.
[ONE Original Android Development] IndDoc:
Yes, that's how it was for me even in r7 as well. I flashed the UKM 3.8.1 from this thread, the one for this kernel. I recently did a clean flash and then just your kernel. Same thing. I just assumed it's a known bug!
[ONE Original Android Development] Hash code:
Does the kernel need to support color settings???..... I just switched to boeffla for testing purpose and bam all I can see is rgb settings in the app..... No settings for hue,saturation etc
[ONE Original Android Development] abhi08638:
Yes so far I think only Render, AK, and TYR support it
[ONE Original Android Development] Hash code:
Oh Kk....ty man...
[ONE Original Android Development] 1337jay:
Updated my rom, flashed R8 and UKM but Synapse gives me the Device Not Supported error. Does anyone know how to solve this? Tried re-flashing UKM but still the same.
[ONE Original Android Development] endriuss:
But what about standard screen color calibration available under screen settings in all cm based roms? Have you tried this. Im using this as a good substitute. Try to find out where do you have this in the rom you are using.

Sorry for the OT.
[ONE Original Android Development] RenderBroken:
[MENTION=5912374]1337jay[/MENTION]

It's an issue with euphoria I believe. Not 100 percent certain. But I will say a quick search would have netted the results you are looking for.

In terminal

su

uci

uci reset

uci

I have added a button to my newest ukm build that I am working in that would fix this.
[ONE Original Android Development] 1337jay:
Thank you, it worked. I tried searching but did not find this particular solution..glad to be back in the game! :P
[ONE Original Android Development] Hiro Nakamura:
You tried render's ukm on his website yet?
[ONE Original Android Development] mnhs1010:
This kernel supports multi rom?
[ONE Original Android Development] _ASSASSIN_:
read the OP bud. Says it right there

* KEXEC Support (MultiRom)
[ONE Original Android Development] RenderBroken:
New Build Released! R9

Download

Things to look for in this build:

Looks like:

video: mdss: Report PCC values from pp registers

Has made the back-light play a little bit better. Seems work with better response and smoothness.

Updated Interactive further.

Really just brought inline with CM

Changelog:

R9:

b150e81 (HEAD, origin/cm-12.0, origin/HEAD, r9, cm-12.0) ipv4: Missing sk_nulls_node_init() in ping_unhash().

9a7d8d6 video: mdss: Report PCC values from pp registers

e71c58c CHROMIUM: cpufreq: interactive: calculate load before freq change

9718e44 cpufreq: interactive: Rearm governor timer at max freq

104945b CHROMIUM: Replace obsolete strict_strtoul calls.

7f74694 Revert "ASoC: es325: Import Oppo Audience ES325 driver"

9d97b43 CHROMIUM: cpufreq: interactive: free above_hispeed_delay on exit

dce19cdd (r8) Build: update Build Script

46694f8 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
[ONE Original Android Development] Norapapa:
I never change anything in Synapse. Are these settings correct.?
[ONE Original Android Development] demon507:
No they are not, for stock values slider should be at 0.
[ONE Original Android Development] Norapapa:
What exactly do I have to change?
[ONE Original Android Development] RenderBroken:
You need to change them to 0 like the user above said. More specifically:

AC Charge Level
[ONE Original Android Development] alexbk66:
Off topic: you can disable proximity check for DT2W completely, or you can use Prox Sensor Calibrator to adjust sencitivity.
[ONE Original Android Development] Norapapa:
The lowest position is 100mA. 0 will not do.
[ONE Original Android Development] RenderBroken:
OK I see what the problem is. I am using a new version of UKM that I have been testing. It will work for you. One sec and I will upload it
[ONE Original Android Development] alexbk66:
It's current, not voltage
[ONE Original Android Development] RenderBroken:
Uploaded new Render-UKM build!

Get it here:

http://renderserver.net/devs/RenderBroken/Render-UKM/Render-UKM-3.8.1.4.zip

Not sure of all the changes from the last build. Main things are, Live Freq readout at the top of the CPU Tab, Charge Control Updated to use the new behavior, and added a button that resets the UCI file when you flash and it says Device not supported. Just to make it easier to go from build to build. It has to deal with Euphoria.
[ONE Original Android Development] _ASSASSIN_:
Random question, but is software CRC disabled by default?
[ONE Original Android Development] RenderBroken:
I dont remember lol. I would have to dig for the tunable and check
[ONE Original Android Development] Hash code:
True.I know that..... But abhis profiles are eye catching which require min,hue,saturation etc settings and its not see in cyanogen color settings.... But when a kernel doesn't support them all I do is set vivid .....
[ONE Original Android Development] Norapapa:
Charging work now. Euphoria + ukm+ r9 ac charge level 0
[ONE Original Android Development] Almayce:
Unfortunately SODs are still present on my end. Dunno why. And every time I have to hard reboot all the apps optimize on the next boot. Pretty annoying. It bothers me coz I found unbelieveable level of smoothness with your kernel. What does one have to do to get rid of those? Any specific settings? Voltages?
[ONE Original Android Development] 1ceb0x:
Wow.... interactive governor ia really smooth in R9. Cannot wait to see what kind of battery backup we can get with it. Thank you [MENTION=5438598]RenderBroken[/MENTION]!
[ONE Original Android Development] clockworkstop:
[MENTION=5438598]RenderBroken[/MENTION] What do you think of integrating UKM into your kernel like [MENTION=3685904]ak[/MENTION] did? His new version also solves the problem it has with Euphoria.
[ONE Original Android Development] venky716:
It has already been done, try the updated ukm (.4) from OP.

Edit : Meant to say the problem with Euphoria rom has been solved with the new ukm but it has not been integrated yet into the kernel zip.
[ONE Original Android Development] RenderBroken:
Well I use close to stock with 0 issues and undervolted by 65mv. What exactly are you changing if anything?

Not gonna happen. I have gone the route of including Synapse files in my ramdisk and its a freaking pain. Because when you times that by 3 different devices I build for I would have to make changes then make the same changes (Commit) to each of my kernels files (Ramdisk/AnyKernel). I would rather keep going the route of making 1 Flavored UKM zip that can be flashed on all of my kernels and more! I am actually coding my changes so that they can be used on any other kernel that you could use UKM with before. I have thought about it but came to the decision that its not that hard to flash one more zip when flashing my new builds. Hell, even the settings stay. Still thanks for asking cuz i know others were thinking the same.
[ONE Original Android Development] Pradhan_89:
R9 is running great here. Good work [MENTION=5438598]RenderBroken[/MENTION] :)
[ONE Original Android Development] Almayce:
Okay gotta report r9 working well here without no sods at all. Dunno what you changed, but it worked :D
[ONE Original Android Development] smoki3:
I think all the problems with sod are related to the proximity sensor. It get some "sod" but if I put my phone in the pocket and put it out again the phone wake up. Its mysterious, but it work all the time. I tried to put my hand over the sensor but this doesn't work. Maybe its related to tampered glass too.
[ONE Original Android Development] schaggo:
As by my report, I never had SOD up until a couple days ago, where I had several in a row using your CM12.1 build, smoki3. After that, not a single one anymore.

If it is the proximity sensor, then the settings do not get respected by the system. I have proximity check set to off ever since the CM12 nightlies dropped in february (with it on, I can't use the phone for navigation in my waterproof case on my motorbike). I also have all gestures disabled. Yet had those SOD a couple days ago. Dunno, mysterious thing this all is, somehow... :\
[ONE Original Android Development] clockworkstop:
I'm a bit confused by benchmark scores. If they are way below average, should I be concerned?
[ONE Original Android Development] 1337jay:
Not at all. Becchmark scores mean nothing, all that matters is user experience.
[ONE Original Android Development] RenderBroken:
Are you running default setup? If so then that would be why. I have tuned my default settings to be smarter than your average bear. In that, if you use an app like Kernel Aduitor, you will see mainly only 2 cores being used EVEN when running a benchmark. SmartMAX really excels at an amazing user experience while keeping it battery friendly. If you want that fake scores you get from running a stock kernel with MPDecision, then just set the governor to performance and online all 4 cores. CM uses their Performance profiles to do such a thing. I don't. I have tuned it so I can achieve the same level of performance (And more I feel) with less battery consumed and lest hot(un)plugging. For this reason, this is why some Devs don't care at all about Benchmarks. I think they are a great tool but not the end all be all. To kinda see what I mean about the number of cores online during certain workload, try just changing the governor to interactive and you will instantly see the number of cores used has gone way up when opening an app or scrolling and such. Same with Benchmarks.
[ONE Original Android Development] 1337jay:
I have been using this kernel for a few days now and it's awesome. There is only one issue that is really frustrating - touchscreen response seems to be slow/lagging sometimes..after a few minutes or locks it becomes normal again. I don't really know how to describe it, it just won't register touches or verly slowly.

Anyone else experiencing this or knows a fix? Thanks.

EDIT: Was not having this issue on stock or any other kernel.
[ONE Original Android Development] NuLLV01D:
I am not facing any of these touch issues, but you could try using the Touch Fixer app from the Themes and Apps section as it seems to work for many users
[ONE Original Android Development] 1337jay:
Thanks, downloaded and testing now. Will report back soon (hour or two).

EDiT: Still having the same issue even with that app.
[ONE Original Android Development] RenderBroken:
Are you enabling Smart Cover in Synapse? I have seen this before and its related to turning that on. I have seen in a friends log that it was like turning on and off all the time. Just something to look into.
[ONE Original Android Development] 1337jay:
No, I'm not running all stock except for -65mV global undervolt - but the issue was there before undervolting too. Scrolling also seems to be slow when that happens, it will only scroll a few lines and not to the bottom as it should when you pull fast.

PS: Wanted to share todays results, just finished my shift at work.
[ONE Original Android Development] thedao:
Render is right, i once turned it on and my phone went nuts until i rebooted it
[ONE Original Android Development] endriuss:
I've experienced the same issue. This is not a big problem and you will not notice this if you didn't try the other kernel but definitely the small issue is here.
[MENTION=5438598]RenderBroken[/MENTION]: In order to help you understand the issue you can try if you want/have time to switch for a while to Euphoria's default kernel (I think you are using Euphoria, aren't you?) and try to scroll in your contacts or scroll on some website in chrome browser/ or another browser. My expression is that in your kernel there is something strange with the touch sensitivity.

I don't have this issue neither using stock nor AK kernel. Maybe they are using different touch drivers?...
[ONE Original Android Development] Cris7ianO:
Am running latest render ukm 3.8.4 but am not able to find that option xD where should it be? :)

Sent from my Bacon
[ONE Original Android Development] thedao:
Under the tab, wake in synapse at the bottom
[ONE Original Android Development] Cris7ianO:
Damn of course xD thanks :) must have overseen it quite a few times there at the bottom :rolleyes:

Sent from my Bacon
[ONE Original Android Development] MBurns2:
Msm by myfluxi+smartmax+render optimization=awesome combo..

I m having the best battery life without any lags..thanks a lot [MENTION=5438598]RenderBroken[/MENTION]
[ONE Original Android Development] Flak:
Clean flash of 5/3 Blisspop and RenderKernel R9. Had been running fine until this morning. Double tap to wake didn't do anything, waited a min or so and tried the power button. Still didn't wake, so I waited and tried double taping again. The phone then did a soft reboot (no one plus animation just the blisspop boot animation) and now the phone is fine again.

Attached is the last kmsg I grabbed after that reboot.
[ONE Original Android Development] RenderBroken:
Then could you grab some logs for me after it happens using Syslog? Thanks!

Nope, same touch drivers and such. But the problem is, if it was my kernel then I too should have the issue along with many others. I agree there is a problem but I am not convinced that it is with my kernel. I would like some logs from you too if you happen to have a chance. I would love to resolve the issue if its with my kernel or not. I work in IT and with computers, an issue occurs, it usually will occur pretty uniformly. Meaning that something like this scrolling issue should happen for everyone all the time. I also keep in mind the total number of ppl that have downloaded my kernel and I assume the flashed it, and the number of ppl actually reporting an issue is such a small percentage compare to those who have downloaded my kernel. I know ppl could have an issue and not report it but they have all found my kernel through XDA (Or some other site that someone ported it to lol) and thus know they can report an issue. So with all things considered its hard for me to believe that it is specifically my kernel but I will not completely rule it out. I am pretty open minded and if there is an issue I like to take it on instead of just blame users. Thanks for the info and if you can, logs would be nice.

PS: I do know that there was an issue with scroll lagging reported but it was rom side. I am not sure if that plays into this or is some sort of trigger bu its worth noting.
[ONE Original Android Development] 1337jay:
I have made two logs just to be sure, hopefully this helps.
[ONE Original Android Development] RenderBroken:
Sweet! Thanks!
[ONE Original Android Development] Zephyr!:
How to block this?
[ONE Original Android Development] Nandeh:
Looks like if fingerprint scanner is causing a unwanted wakelock... You can greenify it or block the especific wakelock if the ROM can do it and if it doesn't affect another apps....
[ONE Original Android Development] 1337jay:
Greenify Google+ or just try to uninstall and see if it helps.
[ONE Original Android Development] endriuss:
I was trying to reproduce the issue but without sucess... I was flashing different version of your ukm, restarting phone many times, changing many values in synapse, changing governors, hotplugs... Your kerner works blazing fast and rock stable. The issues with touch response/scrolling was not kernel related for sure. Maybe I had something messed up with Synapse or UKM... Sorry for the confusion.
[ONE Original Android Development] RenderBroken:
No sweat bro. I like to explain things for those that are curious or want to learn. Not really school anyone. I appreciate the help in narrowing it down, as I said I am not one to side step an issue. I really would like to get to the bottom of it and help the respective dev get it resolved because lag sux. Thanks again!
[ONE Original Android Development] schaggo:
Speaking of lag, or rather the absence thereof: I'm experimenting with Intellimm and Smartmax the last couple days and cannot decide. Interested in what others might have to say.

Going by the letter, smartmax is very light on your battery yet upholds a somewhat pleasant experience. Intellimm should also be light on the battery yet put a bit more juice in upholding a nice experience.

Now, whenever I sticked with the one governor for a while and feel I lost too much juice/time and switch to the other gov, I am under the impression its less fluid and get frustrated. After being on this gov for s while and then going back to the previous one because I feel it used too much juice, I feel the now new one is lagging and the one left behind - once doomed laggy and crappy :D - felt better.

So Render, which should be the more balanced gov from a technical point of view, and you guys, who used both, which one would you describe as "superior"? Where superior means, generally speaking, overall more responsive, pleasant yet still battery efficient.
[ONE Original Android Development] Zephyr!:
Random reboot. Please have a look. Latest kernel with all stock settings. Governor : smartmax

https://app.box.com/s/cwx23ui0kj9tf4fbzavynrr0ilqk6fuk
[ONE Original Android Development] clockworkstop:
I can confirm this, especially on previous builds of this kernel. The newest release seems to have solved the problem, although I still think my touchscreen isn't as responsive as it used to be. Used to drive me insane on the older versions.
[ONE Original Android Development] epiquiem:
Hey [MENTION=5438598]RenderBroken[/MENTION], any chance you could start including the release name in the kernel version? e.g,

Linux version 3.4.107~Render-Kernel (RenderBroken@RenderServer.net) (gcc blahblah ) #1

to something like

Linux version 3.4.107~Render-Kernel (RenderBroken@RenderServer.net) (gcc blahblah ) [B]#9[/B]

I'm writing an OTA app for RK, and I can't distinguish the current kernel version. Even if I wasn't, I rarely remember which version I have :p.

Thanks!
[ONE Original Android Development] RenderBroken:
I am sure I can come up with something. Also when you are done with the app, let me give it a shot. I would love to link your work!
[ONE Original Android Development] critofur:
Since you said "noob friendly" :) Not sure if this could be something you could do with a kernel and perhaps some special added settings in the ROM? But I'd like to be able to limit certain applications to using less CPU - possibly throttling down battery hogs like Clash of Clans? Would certainly want this to be on a per-app basis. Also how about things like "core affinity". (Like in Windows you can assign certain programs to particular CPU cores).

I have no idea if perhaps recent versions of Android are particularly good at balancing different threads accross multiple cores such that an app might be mostly using one core while wifi + networking is put on another core etc?

I see all these kernels each time I'm poking around looking at ROMs for whichever phone I happen to have, and I'm wondering, aren't there benchmark graphs where various kernels are compared to show us how the kernels compare at particular tasks, battery life, etc?
[ONE Original Android Development] Renosh:
A few apps I've found can do this. FKUpdater, Faux123 Kernel Enhancement Pro and there's an xposed module called Performance Profile (free). You can limit the CPU frequency, input boost frequency, GPU and thermal throttle temp in games like Clash of Clans.

There was another app called per-app modes by [MENTION=3292224]franciscofranco[/MENTION] but he abandoned that project. I wish Synapse had this functionality, but due to this feature I use one of these apps I mentioned
[ONE Original Android Development] 1ceb0x:
Render optimizations? Are you using Boeffla kernel app with this kernel? If not, from where did you find the Render optimizations? Is it in Synapse?

Btw guys - if you have lag when scrolling, try to increase the cpu boost of all 4 cores to 1.2 ghz. As default it is 1.1 ghz, but 1.2 works more fluidly for me. Just a thought.
[ONE Original Android Development] MBurns2:
it's a metaphor for saying Render "touch" :)
[ONE Original Android Development] RenderBroken:
Well, the question of the per-app modes has been answered. As for Core Affinity, that is not really an option because of hotplugging. You can do such a thing in windows because their cores never get unplugged. They are always online. Also the way we have to scheduler workload would supersede anything like that as well.
[ONE Original Android Development] Flak:
Experienced another soft reboot this morning after the phone failed to wake.
[ONE Original Android Development] Nandeh:
It's really strange the issues you report. I haven't got no one since first release I tried. And I have tested combined with a lot of different ROMs.

It could be possible that your issues be related with hardware failures?

Just asking...
[ONE Original Android Development] RenderBroken:
I could not really see anything from the log you gave me earlier but I would like more. Sometimes it takes time to catch relavant info.
[ONE Original Android Development] critofur:
Which of these options will work well in Android Lollipop 5.1.x?